linux-toradex.git/drivers/md/bcache/super.c, branch v3.11 Linux kernel for Apalis and Colibri modules bcache: Allocation kthread fixes 2013-07-12T07:22:49+00:00 Kent Overstreet kmo@daterainc.com 2013-07-11T01:31:58+00:00 79826c35eb99cd3c0873b8396f45fa26c87fb0b0 The alloc kthread should've been using try_to_freeze() - and also there was the potential for the alloc kthread to get woken up after it had shut down, which would have been bad. Signed-off-by: Kent Overstreet <kmo@daterainc.com> 
The alloc kthread should've been using try_to_freeze() - and also there
was the potential for the alloc kthread to get woken up after it had
shut down, which would have been bad.

Signed-off-by: Kent Overstreet <kmo@daterainc.com>
bcache: Shutdown fix 2013-07-12T07:22:47+00:00 Kent Overstreet kmo@daterainc.com 2013-07-11T04:03:25+00:00 5caa52afc5abd1396e4af720469abb5843a71eb8 Stopping a cache set is supposed to make it stop attached backing devices, but somewhere along the way that code got lost. Fixing this mainly has the effect of fixing our reboot notifier. Signed-off-by: Kent Overstreet <kmo@daterainc.com> Cc: linux-stable <stable@vger.kernel.org> # >= v3.10 
Stopping a cache set is supposed to make it stop attached backing
devices, but somewhere along the way that code got lost. Fixing this
mainly has the effect of fixing our reboot notifier.

Signed-off-by: Kent Overstreet <kmo@daterainc.com>
Cc: linux-stable <stable@vger.kernel.org> # >= v3.10
bcache: Fix a sysfs splat on shutdown 2013-07-12T07:22:47+00:00 Kent Overstreet kmo@daterainc.com 2013-07-11T04:25:02+00:00 c9502ea4424b31728703d113fc6b30bfead14633 If we stopped a bcache device when we were already detaching (or something like that), bcache_device_unlink() would try to remove a symlink from sysfs that was already gone because the bcache dev kobject had already been removed from sysfs. So keep track of whether we've removed stuff from sysfs. Signed-off-by: Kent Overstreet <kmo@daterainc.com> Cc: linux-stable <stable@vger.kernel.org> # >= v3.10 
If we stopped a bcache device when we were already detaching (or
something like that), bcache_device_unlink() would try to remove a
symlink from sysfs that was already gone because the bcache dev kobject
had already been removed from sysfs.

So keep track of whether we've removed stuff from sysfs.

Signed-off-by: Kent Overstreet <kmo@daterainc.com>
Cc: linux-stable <stable@vger.kernel.org> # >= v3.10
bcache: Advertise that flushes are supported 2013-07-12T07:22:46+00:00 Kent Overstreet kmo@daterainc.com 2013-07-11T01:44:40+00:00 54d12f2b4fd0f218590d1490b41a18d0e2328a9a Whoops - bcache's flush/FUA was mostly correct, but flushes get filtered out unless we say we support them... Signed-off-by: Kent Overstreet <kmo@daterainc.com> Cc: linux-stable <stable@vger.kernel.org> # >= v3.10 
Whoops - bcache's flush/FUA was mostly correct, but flushes get filtered
out unless we say we support them...

Signed-off-by: Kent Overstreet <kmo@daterainc.com>
Cc: linux-stable <stable@vger.kernel.org> # >= v3.10
bcache: Send label uevents 2013-06-27T04:58:06+00:00 Gabriel de Perthuis g2p.code@gmail.com 2013-06-08T22:54:48+00:00 ab9e14002e271eba41f7f9ab7e9b03cac4adc22d Signed-off-by: Gabriel de Perthuis <g2p.code@gmail.com> Signed-off-by: Kent Overstreet <koverstreet@google.com> 
Signed-off-by: Gabriel de Perthuis <g2p.code@gmail.com>
Signed-off-by: Kent Overstreet <koverstreet@google.com>
bcache: Send a uevent with a cached device's UUID 2013-06-27T04:58:05+00:00 Gabriel de Perthuis g2p.code@gmail.com 2013-06-07T21:27:01+00:00 a25c32bedeff3573b53572b87bcafe10ec5b75a9 Signed-off-by: Gabriel de Perthuis <g2p.code@gmail.com> 
Signed-off-by: Gabriel de Perthuis <g2p.code@gmail.com>
bcache: Track dirty data by stripe 2013-06-27T04:57:23+00:00 Kent Overstreet koverstreet@google.com 2013-06-05T13:21:07+00:00 279afbad4e54acbd61bf88a54a73af3bbfdeb5dd 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 <koverstreet@google.com> 
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 <koverstreet@google.com>
bcache: Initialize sectors_dirty when attaching 2013-06-27T00:09:16+00:00 Kent Overstreet koverstreet@google.com 2013-05-12T00:07:26+00:00 444fc0b6b167ed164e7436621a9d095e042644dd Previously, dirty_data wouldn't get initialized until the first garbage collection... which was a bit of a problem for background writeback (as the PD controller keys off of it) and also confusing for users. This is also prep work for making background writeback aware of raid5/6 stripes. Signed-off-by: Kent Overstreet <koverstreet@google.com> 
Previously, dirty_data wouldn't get initialized until the first garbage
collection... which was a bit of a problem for background writeback (as
the PD controller keys off of it) and also confusing for users.

This is also prep work for making background writeback aware of raid5/6
stripes.

Signed-off-by: Kent Overstreet <koverstreet@google.com>
bcache: Improve lazy sorting 2013-06-27T00:09:16+00:00 Kent Overstreet koverstreet@google.com 2013-05-11T22:59:37+00:00 6ded34d1a54c046a45db071d3cb7b37bd0a4a31f The old lazy sorting code was kind of hacky - rewrite in a way that mathematically makes more sense; the idea is that the size of the sets of keys in a btree node should increase by a more or less fixed ratio from smallest to biggest. Signed-off-by: Kent Overstreet <koverstreet@google.com> 
The old lazy sorting code was kind of hacky - rewrite in a way that
mathematically makes more sense; the idea is that the size of the sets
of keys in a btree node should increase by a more or less fixed ratio
from smallest to biggest.

Signed-off-by: Kent Overstreet <koverstreet@google.com>
bcache: Rip out pkey()/pbtree() 2013-06-27T00:09:15+00:00 Kent Overstreet koverstreet@google.com 2013-05-15T03:33:16+00:00 85b1492ee113486d871de7676a61f506a43ca475 Old gcc doesnt like the struct hack, and it is kind of ugly. So finish off the work to convert pr_debug() statements to tracepoints, and delete pkey()/pbtree(). Signed-off-by: Kent Overstreet <koverstreet@google.com> 
Old gcc doesnt like the struct hack, and it is kind of ugly. So finish
off the work to convert pr_debug() statements to tracepoints, and delete
pkey()/pbtree().

Signed-off-by: Kent Overstreet <koverstreet@google.com>