Prev: [01/11] nvram: Fix write beyond end condition; prove to gcc copy is safe
Next: [[PATCH 06/11]] viafb: rework output device routing
From: Greg KH on 11 Aug 2010 20:00
2.6.27-stable review patch. If anyone has any objections, please let us know.

------------------

From: Kay Sievers <kay.sievers(a)vrfy.org>

commit f1d0b063d993527754f062c589b73f125024d216 upstream.

Devices which share the same queue, like floppies and mtd devices, get
registered multiple times in the bdi interface, but bdi accounts only the
last registered device of the devices sharing one queue.

On remove, all earlier registered devices leak, stay around in sysfs, and
cause "duplicate filename" errors if the devices are re-created.

This prevents the creation of multiple bdi interfaces per queue, and the
bdi device will carry the dev_t name of the block device which is the
first one registered, of the pool of devices using the same queue.

[akpm(a)linux-foundation.org: add a WARN_ON so we know which drivers are misbehaving]
Tested-by: Peter Korsgaard <jacmet(a)sunsite.dk>
Acked-by: Peter Zijlstra <a.p.zijlstra(a)chello.nl>
Signed-off-by: Kay Sievers <kay.sievers(a)vrfy.org>
Cc: David Woodhouse <dwmw2(a)infradead.org>
Signed-off-by: Andrew Morton <akpm(a)linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds(a)linux-foundation.org>
Cc: Ben Hutchings <bhutchings(a)solarflare.com>
Signed-off-by: Greg Kroah-Hartman <gregkh(a)suse.de>

---
mm/backing-dev.c | 3 +++
1 file changed, 3 insertions(+)

--- a/mm/backing-dev.c
+++ b/mm/backing-dev.c
@@ -176,6 +176,9 @@ int bdi_register(struct backing_dev_info
int ret = 0;
struct device *dev;

+ if (WARN_ON(bdi->dev))
+ goto exit;
+
va_start(args, fmt);
dev = device_create_vargs(bdi_class, parent, MKDEV(0, 0), bdi, fmt, args);
va_end(args);


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: [01/11] nvram: Fix write beyond end condition; prove to gcc copy is safe
Next: [[PATCH 06/11]] viafb: rework output device routing