linux-toradex.git/drivers/md/dm-exception-store.c, branch v2.6.35-rc5

dm snapshot: move cow ref from exception store to snap core

2009-12-10T23:52:12+00:00

Store the reference to the snapshot cow device in the core snapshot
code instead of each exception store.  It can be accessed through the
new function dm_snap_cow().  Exception stores should each now maintain a
reference to their parent snapshot struct.

This is cleaner and makes part of the forthcoming snapshot merge code simpler.

Signed-off-by: Mike Snitzer 
Signed-off-by: Alasdair G Kergon 
Reviewed-by: Jonathan Brassow 
Cc: Mikulas Patocka

dm exception store: free tmp_store on persistent flag error

2009-12-10T23:51:52+00:00

Error handling code following a kmalloc should free the allocated data.

Cc: stable@kernel.org
Signed-off-by: Julia Lawall 
Signed-off-by: Alasdair G Kergon

dm snapshot: allow chunk size to be less than page size

2009-10-16T22:18:22+00:00

Allow the snapshot chunk size to be smaller than the page size
The code is now capable of handling this due to some previous
fixes and enhancements.

As the page size varies between computers, prior to this patch,
the chunk size of a snapshot dictated which machines could read it:
Snapshots created on one machine might not be readable on another.

Signed-off-by: Mikulas Patocka 
Reviewed-by: Mike Snitzer 
Reviewed-by: Jonathan Brassow 
Signed-off-by: Alasdair G Kergon

dm snapshot: use unsigned integer chunk size

2009-10-16T22:18:17+00:00

Use unsigned integer chunk size.

Maximum chunk size is 512kB, there won't ever be need to use 4GB chunk size,
so the number can be 32-bit. This fixes compiler failure on 32-bit systems
with large block devices.

Cc: stable@kernel.org
Signed-off-by: Mikulas Patocka 
Signed-off-by: Mike Snitzer 
Reviewed-by: Jonathan Brassow 
Signed-off-by: Alasdair G Kergon

dm exception store: fix failed set_chunk_size error path

2009-10-16T22:18:16+00:00

Properly close the device if failing because of an invalid chunk size.

Cc: stable@kernel.org
Signed-off-by: Mikulas Patocka 
Signed-off-by: Alasdair G Kergon

dm snapshot: fix on disk chunk size validation

2009-09-04T19:40:43+00:00

Fix some problems seen in the chunk size processing when activating a
pre-existing snapshot.

For a new snapshot, the chunk size can either be supplied by the creator
or a default value can be used.  For an existing snapshot, the
chunk size in the snapshot header on disk should always be used.

If someone attempts to load an existing snapshot and has the 'default
chunk size' option set, the kernel uses its default value even when it
is incorrect for the snapshot being loaded.  This patch ensures the
correct on-disk value is always used.

Secondly, when the code does use the chunk size stored on the disk it is
prudent to revalidate it, so the code can exit cleanly if it got
corrupted as happened in
https://bugzilla.redhat.com/show_bug.cgi?id=461506 .

Cc: stable@kernel.org
Signed-off-by: Mikulas Patocka 
Signed-off-by: Alasdair G Kergon

dm exception store: split set_chunk_size

2009-09-04T19:40:41+00:00

Break the function set_chunk_size to two functions in preparation for
the fix in the following patch.

Cc: stable@kernel.org
Signed-off-by: Mikulas Patocka 
Signed-off-by: Alasdair G Kergon

dm exception store: really fix type lookup

2009-06-30T14:18:14+00:00

Fix exception store name handling.

We need to reference exception store by zero terminated string.

Fixes regression introduced in commit f6bd4eb73cdf2a5bf954e497972842f39cabb7e3

Cc: Yi Yang 
Cc: Jonathan Brassow 
Cc: stable@kernel.org
Cc: Andrew Morton 
Signed-off-by: Milan Broz 
Signed-off-by: Alasdair G Kergon

dm exception store: fix exstore lookup to be case insensitive

2009-06-22T09:12:15+00:00

When snapshots are created using 'p' instead of 'P' as the
exception store type, the device-mapper table loading fails.

This patch makes the code case insensitive as intended and fixes some
regressions reported with device-mapper snapshots.

Signed-off-by: Jonathan Brassow 
Cc: stable@kernel.org
Signed-off-by: Alasdair G Kergon

block: Do away with the notion of hardsect_size

2009-05-22T21:22:54+00:00

Until now we have had a 1:1 mapping between storage device physical
block size and the logical block sized used when addressing the device.
With SATA 4KB drives coming out that will no longer be the case.  The
sector size will be 4KB but the logical block size will remain
512-bytes.  Hence we need to distinguish between the physical block size
and the logical ditto.

This patch renames hardsect_size to logical_block_size.

Signed-off-by: Martin K. Petersen 
Signed-off-by: Jens Axboe