linux-stable.git/drivers/md/bcache/request.c, branch v3.12

bcache: Fixed incorrect order of arguments to bio_alloc_bioset()

2013-10-23T06:55:36+00:00

Signed-off-by: Kent Overstreet 
Cc: linux-stable  # >= v3.10
Signed-off-by: Linus Torvalds

bcache: Fix a null ptr deref regression

2013-10-11T01:17:39+00:00

Commit c0f04d88e46d ("bcache: Fix flushes in writeback mode") was fixing
a reported data corruption bug, but it seems some last minute
refactoring or rebasing introduced a null pointer deref.

Signed-off-by: Kent Overstreet 
Cc: linux-stable  # >= v3.10
Reported-by: Gabriel de Perthuis 
Signed-off-by: Linus Torvalds

bcache: Fix flushes in writeback mode

2013-09-24T21:41:43+00:00

In writeback mode, when we get a cache flush we need to make sure we
issue a flush to the backing device.

The code for sending down an extra flush was wrong - by cloning the bio
we were probably getting flags that didn't make sense for a bare flush,
and also the old code was firing for FUA bios, for which we don't need
to send a flush to the backing device.

This was causing data corruption somehow - the mechanism was never
determined, but this patch fixes it for the users that were seeing it.

Signed-off-by: Kent Overstreet 
Cc: linux-stable  # >= v3.10
Signed-off-by: Linus Torvalds

bcache: Advertise that flushes are supported

2013-07-12T07:22:46+00:00

Whoops - bcache's flush/FUA was mostly correct, but flushes get filtered
out unless we say we support them...

Signed-off-by: Kent Overstreet 
Cc: linux-stable  # >= v3.10

bcache: Use standard utility code

2013-07-01T21:43:53+00:00

Some of bcache's utility code has made it into the rest of the kernel,
so drop the bcache versions.

Bcache used to have a workaround for allocating from a bio set under
generic_make_request() (if you allocated more than once, the bios you
already allocated would get stuck on current->bio_list when you
submitted, and you'd risk deadlock) - bcache would mask out __GFP_WAIT
when allocating bios under generic_make_request() so that allocation
could fail and it could retry from workqueue. But bio_alloc_bioset() has
a workaround now, so we can drop this hack and the associated error
handling.

Signed-off-by: Kent Overstreet

bcache: FUA fixes

2013-07-01T21:42:47+00:00

Journal writes need to be marked FUA, not just REQ_FLUSH. And btree node
writes have... weird ordering requirements.

Signed-off-by: Kent Overstreet

bcache: Write out full stripes

2013-06-27T04:58:04+00:00

Now that we're tracking dirty data per stripe, we can add two
optimizations for raid5/6:

 * If a stripe is already dirty, force writes to that stripe to
   writeback mode - to help build up full stripes of dirty data

 * When flushing dirty data, preferentially write out full stripes first
   if there are any.

Signed-off-by: Kent Overstreet

bcache: Track dirty data by stripe

2013-06-27T04:57:23+00:00

To make background writeback aware of raid5/6 stripes, we first need to
track the amount of dirty data within each stripe - we do this by
breaking up the existing sectors_dirty into per stripe atomic_ts

Signed-off-by: Kent Overstreet

bcache: Fix/revamp tracepoints

2013-06-27T00:09:15+00:00

The tracepoints were reworked to be more sensible, and fixed a null
pointer deref in one of the tracepoints.

Converted some of the pr_debug()s to tracepoints - this is partly a
performance optimization; it used to be that with DEBUG or
CONFIG_DYNAMIC_DEBUG pr_debug() was an empty macro; but at some point it
was changed to an empty inline function.

Some of the pr_debug() statements had rather expensive function calls as
part of the arguments, so this code was getting run unnecessarily even
on non debug kernels - in some fast paths, too.

Signed-off-by: Kent Overstreet

bcache: Take data offset from the bdev superblock.

2013-04-21T00:56:12+00:00

Add a new superblock version, and consolidate related defines.

Signed-off-by: Gabriel de Perthuis 
Signed-off-by: Kent Overstreet