From: Russell Cattelan <cattelan@thebarn.com>
To: linux-kernel@vger.kernel.org
Subject: Test12 ll_rw_block error.
Date: Thu, 14 Dec 2000 20:02:17 -0600 [thread overview]
Message-ID: <3A397BA9.CB0EC8E5@thebarn.com> (raw)
This would seem to be an error on the part of ll_rw_block.
Setting b_end_io to a default handler without checking to see
a callback has already been defined defeats the purpose of having
a function op.
void ll_rw_block(int rw, int nr, struct buffer_head * bhs[])
{
@@ -928,7 +1046,8 @@
if (test_and_set_bit(BH_Lock, &bh->b_state))
continue;
- set_bit(BH_Req, &bh->b_state);
+ /* We have the buffer lock */
+ bh->b_end_io = end_buffer_io_sync;
switch(rw) {
case WRITE:
-Russell Cattelan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-12-15 2:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-15 2:02 Russell Cattelan [this message]
2000-12-15 2:48 ` Test12 ll_rw_block error Linus Torvalds
[not found] <3A398D58.92BBC9A4@thebarn.com>
2000-12-15 3:28 ` Linus Torvalds
[not found] <3A398F84.2CD3039D@thebarn.com>
2000-12-15 6:20 ` Linus Torvalds
2000-12-15 7:00 ` Alexander Viro
2000-12-15 9:14 ` Chris Mason
2000-12-17 0:54 ` Russell Cattelan
2000-12-17 12:20 ` Chris Mason
2000-12-15 10:51 ` Stephen C. Tweedie
2000-12-15 19:04 ` Linus Torvalds
2000-12-17 1:08 ` Russell Cattelan
2000-12-18 11:44 ` Stephen C. Tweedie
2000-12-17 2:38 ` Marcelo Tosatti
2000-12-18 11:46 ` Stephen C. Tweedie
2000-12-19 14:05 ` Marcelo Tosatti
2000-12-19 16:43 ` Daniel Phillips
2000-12-19 17:18 ` Marcelo Tosatti
2000-12-19 17:40 ` Christoph Hellwig
2000-12-17 0:51 ` Russell Cattelan
2000-12-17 0:21 ` Russell Cattelan
-- strict thread matches above, loose matches on Subject: below --
2000-12-16 0:58 Jeff Chua
2000-12-16 1:12 ` Linus Torvalds
2000-12-16 17:13 ` Chris Mason
2000-12-16 19:07 ` Linus Torvalds
2000-12-16 19:35 ` Chris Mason
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3A397BA9.CB0EC8E5@thebarn.com \
--to=cattelan@thebarn.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.