* [PATCH] 2.5.44 Fix uninitialized device struct w/ add_disk()
@ 2002-10-19 8:11 Andres Salomon
2002-10-19 8:53 ` Alexander Viro
0 siblings, 1 reply; 2+ messages in thread
From: Andres Salomon @ 2002-10-19 8:11 UTC (permalink / raw)
To: linux-kernel
[-- Attachment #1: Type: text/plain, Size: 862 bytes --]
This occurs w/ 2.5 device-mapper; add_disk() is called (w/ a possibly
invalid gendisk). add_disk() calls register_disk(), which constructs
the device struct (gendisk::disk_dev). First, the bus_id field is
initialized, and then device_add() is called. However, device_add()
does no initialization of the device struct. So, since the
gendisk::disk_dev::parent list is NULL, the gendisk::disk_dev::node
field is never initialized. Later on in device_add(), if an error has
occurred, list_del_init(&dev->node) is called; dev->node is {NULL,NULL},
and an oops occurs.
Instead of calling device_add(), my patch makes register_disk() call
device_register(). This appear to do the same thing as device_add(),
but initializes the device struct before calling device_add().
--
It's not denial. I'm just selective about the reality I accept.
-- Bill Watterson
[-- Attachment #2: check.c.diff --]
[-- Type: text/plain, Size: 377 bytes --]
--- a/fs/partitions/check.c 2002-10-19 03:56:00.000000000 -0400
+++ a/fs/partitions/check.c 2002-10-19 03:56:10.000000000 -0400
@@ -455,7 +455,7 @@
s = strchr(dev->bus_id, '/');
if (s)
*s = '!';
- device_add(dev);
+ device_register(dev);
device_create_file(dev, &disk_attr_dev);
device_create_file(dev, &disk_attr_range);
device_create_file(dev, &disk_attr_size);
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PATCH] 2.5.44 Fix uninitialized device struct w/ add_disk()
2002-10-19 8:11 [PATCH] 2.5.44 Fix uninitialized device struct w/ add_disk() Andres Salomon
@ 2002-10-19 8:53 ` Alexander Viro
0 siblings, 0 replies; 2+ messages in thread
From: Alexander Viro @ 2002-10-19 8:53 UTC (permalink / raw)
To: Andres Salomon; +Cc: linux-kernel
On Sat, 19 Oct 2002, Andres Salomon wrote:
> This occurs w/ 2.5 device-mapper; add_disk() is called (w/ a possibly
> invalid gendisk). add_disk() calls register_disk(), which constructs
> the device struct (gendisk::disk_dev). First, the bus_id field is
> initialized, and then device_add() is called. However, device_add()
> does no initialization of the device struct. So, since the
> gendisk::disk_dev::parent list is NULL, the gendisk::disk_dev::node
> field is never initialized. Later on in device_add(), if an error has
> occurred, list_del_init(&dev->node) is called; dev->node is {NULL,NULL},
> and an oops occurs.
>
> Instead of calling device_add(), my patch makes register_disk() call
> device_register(). This appear to do the same thing as device_add(),
> but initializes the device struct before calling device_add().
Wrong. If device-mapper doesn't create gendisk with alloc_disk() - it's
their bug; if it does - initialization is already done at alloc_disk()
time.
Fix driver instead of breaking generic code.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2002-10-19 8:47 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-10-19 8:11 [PATCH] 2.5.44 Fix uninitialized device struct w/ add_disk() Andres Salomon
2002-10-19 8:53 ` Alexander Viro
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®