diff options
| author | Kent Overstreet <kmo@daterainc.com> | 2013-09-23 23:17:36 -0700 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2013-09-24 14:41:43 -0700 |
| commit | c0f04d88e46d14de51f4baebb6efafb7d59e9f96 (patch) | |
| tree | 0d4a828d7eb2d482b0db847b9469ba29924ae576 /kernel/latencytop.c | |
| parent | 84786438ed17978d72eeced580ab757e4da8830b (diff) | |
| download | linux-c0f04d88e46d14de51f4baebb6efafb7d59e9f96.tar.bz2 | |
bcache: Fix flushes in writeback mode
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 <kmo@daterainc.com>
Cc: linux-stable <stable@vger.kernel.org> # >= v3.10
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'kernel/latencytop.c')
0 files changed, 0 insertions, 0 deletions