__make_request() bug and a fix variant
From: Andrew Zabolotny (zap_at_homelink.ru)
Date: 09/19/03
- Previous message: Greg KH: "Re: irq 11: nobody cared! is back"
- Next in thread: Jens Axboe: "Re: __make_request() bug and a fix variant"
- Reply: Jens Axboe: "Re: __make_request() bug and a fix variant"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 19 Sep 2003 23:17:32 +0400 To: linux-kernel@vger.kernel.org
Hello!
While developing a driver I found something that I think is a bug in
kernel (I'm using 2.4.20, I just hope it is already fixed in 2.6.x
series). It manifests itself by bread() randomly crashing (in different
places) if called for, say, reading 1024 bytes from block 0 of device
0300 from a driver's module_init() (at least in my very stripped debug
environment, this could differ from system to system).
Here's a somewhat long description of the problem roots:
bread() in the first place calls getblk(), which first tries to find the
requested buffer in hash tables, and if it is not there, it calls
grow_buffers(), the later calls grow_dev_page() and finally that calls
create_buffers(). The later gets a set of free buffer_head's from the
pool, and puts them in a chain attached to a page. Many fields are left
in a indefinite state since they are initialized before usage. The
b_reqnext field is left in a indefinite state as well, and it happens
to be filled with garbage in my case (actually it's a leftover from
previous usage of the buffer_head).
Now when bread() gets this buffer, it is passed to ll_rw_block() which
is passing it to generic_make_request(), and, in turn (for many block
devices including IDE) to __make_request.
And finally, if elevator returns ELEVATOR_NO_MERGE, the b_reqnext field
of the buffer_head structure is left uninitialized! So when b_end_io
(and in turn end_that_request_first) is called, it looks at b_reqnext
and sees there's another bufhead waiting for processing. What happens
next is limited just by your imagination :-)
Also I observed the ELEVATOR_BACK_MERGE case also has the same problem
(bh->b_reqnext is left in a indefinite state). So maybe __make_request
always assumes that b_reqnext is initially NULL? In this case the bug is
in create_buffers which should NULLify this field. In any case, I'm
leaving the final solution up to kernel wizards.
-- Greetings, Andrew P.S. If you reply to this letter, please cc: it to my address since I'm not subscribed to this list. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Previous message: Greg KH: "Re: irq 11: nobody cared! is back"
- Next in thread: Jens Axboe: "Re: __make_request() bug and a fix variant"
- Reply: Jens Axboe: "Re: __make_request() bug and a fix variant"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|