linux-stable.git/drivers/md/bcache, branch v3.10 Linux kernel stable tree bcache: Fix error handling in init code 2013-05-15T07:48:14+00:00 Kent Overstreet koverstreet@google.com 2013-05-15T07:11:26+00:00 f59fce847fc8483508b5028c24e2b1e00523dd88 This code appears to have rotted... fix various bugs and do some refactoring. Signed-off-by: Kent Overstreet <koverstreet@google.com> 
This code appears to have rotted... fix various bugs and do some
refactoring.

Signed-off-by: Kent Overstreet <koverstreet@google.com>
bcache: drop "select CLOSURES" 2013-05-15T07:42:51+00:00 Paul Bolle pebolle@tiscali.nl 2013-05-13T08:35:21+00:00 bbb1c3b5ae6c6286a5e018786be88f126d769543 The Kconfig entry for BCACHE selects CLOSURES. But there's no Kconfig symbol CLOSURES. That symbol was used in development versions of bcache, but was removed when the closures code was no longer provided as a kernel library. It can safely be dropped. Signed-off-by: Paul Bolle <pebolle@tiscali.nl> 
The Kconfig entry for BCACHE selects CLOSURES. But there's no Kconfig
symbol CLOSURES. That symbol was used in development versions of bcache,
but was removed when the closures code was no longer provided as a
kernel library. It can safely be dropped.

Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
bcache: Fix incompatible pointer type warning 2013-05-15T07:42:50+00:00 Emil Goode emilgoode@gmail.com 2013-05-09T20:39:26+00:00 867e1162068eb5632c829d453fd65d6089564f55 The function pointer release in struct block_device_operations should point to functions declared as void. Sparse warnings: drivers/md/bcache/super.c:656:27: warning: incorrect type in initializer (different base types) drivers/md/bcache/super.c:656:27: expected void ( *release )( ... ) drivers/md/bcache/super.c:656:27: got int ( static [toplevel] *<noident> )( ... ) drivers/md/bcache/super.c:656:2: warning: initialization from incompatible pointer type [enabled by default] drivers/md/bcache/super.c:656:2: warning: (near initialization for ‘bcache_ops.release’) [enabled by default] Signed-off-by: Emil Goode <emilgoode@gmail.com> Signed-off-by: Kent Overstreet <koverstreet@google.com> 
The function pointer release in struct block_device_operations
should point to functions declared as void.

Sparse warnings:

drivers/md/bcache/super.c:656:27: warning:
	incorrect type in initializer (different base types)
	drivers/md/bcache/super.c:656:27:
	expected void ( *release )( ... )
	drivers/md/bcache/super.c:656:27:
	got int ( static [toplevel] *<noident> )( ... )

drivers/md/bcache/super.c:656:2: warning:
	initialization from incompatible pointer type [enabled by default]

drivers/md/bcache/super.c:656:2: warning:
	(near initialization for ‘bcache_ops.release’) [enabled by default]

Signed-off-by: Emil Goode <emilgoode@gmail.com>
Signed-off-by: Kent Overstreet <koverstreet@google.com>
bcache: Use bd_link_disk_holder() 2013-05-01T02:14:43+00:00 Kent Overstreet koverstreet@google.com 2013-02-01T15:29:41+00:00 ee66850642efda91d04179cae2414310675a1f73 Signed-off-by: Kent Overstreet <koverstreet@google.com> 
Signed-off-by: Kent Overstreet <koverstreet@google.com>
bcache: Allocator cleanup/fixes 2013-05-01T02:14:40+00:00 Kent Overstreet koverstreet@google.com 2013-05-01T02:14:40+00:00 86b26b824cf5d15d4408b33d6d716104f249e8bd The main fix is that bch_allocator_thread() wasn't waiting on garbage collection to finish (if invalidate_buckets had set ca->invalidate_needs_gc); we need that to make sure the allocator doesn't spin and potentially block gc from finishing. Signed-off-by: Kent Overstreet <koverstreet@google.com> 
The main fix is that bch_allocator_thread() wasn't waiting on
garbage collection to finish (if invalidate_buckets had set
ca->invalidate_needs_gc); we need that to make sure the allocator
doesn't spin and potentially block gc from finishing.

Signed-off-by: Kent Overstreet <koverstreet@google.com>
bcache: Make sure blocksize isn't smaller than device blocksize 2013-04-24T20:07:39+00:00 Kent Overstreet koverstreet@google.com 2013-04-24T04:51:48+00:00 8abb2a5dbadab91f9cae22270054e9ee3b3a1d2f Sanity check to make sure we don't end up doing IO the device doesn't support. Signed-off-by: Kent Overstreet <koverstreet@google.com> 
Sanity check to make sure we don't end up doing IO the device doesn't
support.

Signed-off-by: Kent Overstreet <koverstreet@google.com>
bcache: Fix merge_bvec_fn usage for when it modifies the bvm 2013-04-22T21:44:24+00:00 Kent Overstreet koverstreet@google.com 2013-04-22T21:44:24+00:00 a09ded8edf9ed4009930713e101249084cbcea5c Stacked md devices reuse the bvm for the subordinate device, causing problems... Reported-by: Michael Balser <michael.balser@profitbricks.com> Signed-off-by: Kent Overstreet <koverstreet@google.com> 
Stacked md devices reuse the bvm for the subordinate device, causing
problems...

Reported-by: Michael Balser <michael.balser@profitbricks.com>
Signed-off-by: Kent Overstreet <koverstreet@google.com>
bcache: Correctly check against BIO_MAX_PAGES 2013-04-21T00:57:42+00:00 Kent Overstreet koverstreet@google.com 2013-04-10T22:50:57+00:00 1545f13730be43278ce12f4af7e51b4dee5066a8 bch_bio_max_sectors() was checking against BIO_MAX_PAGES as if the limit was for the total bytes in the bio, not the number of segments. Signed-off-by: Kent Overstreet <koverstreet@google.com> 
bch_bio_max_sectors() was checking against BIO_MAX_PAGES as if the limit
was for the total bytes in the bio, not the number of segments.

Signed-off-by: Kent Overstreet <koverstreet@google.com>
bcache: Hack around stuff that clones up to bi_max_vecs 2013-04-21T00:57:41+00:00 Kent Overstreet koverstreet@google.com 2013-04-20T22:26:31+00:00 bca97adaf522dff0e9ccf2c3f4150a1a7378932a Signed-off-by: Kent Overstreet <koverstreet@google.com> 
Signed-off-by: Kent Overstreet <koverstreet@google.com>
bcache: Set ra_pages based on backing device's ra_pages 2013-04-21T00:57:26+00:00 Kent Overstreet koverstreet@google.com 2013-03-27T18:09:23+00:00 4f0fd955cd13bd94166099db7b31065479d884ed Signed-off-by: Kent Overstreet <koverstreet@google.com> 
Signed-off-by: Kent Overstreet <koverstreet@google.com>