Re: 2.4.11-pre2 fs/buffer.c: invalidate: busy buffer
Neil Brown (email@example.com)
Wed, 3 Oct 2001 17:13:37 +1000 (EST)
On Wednesday October 3, firstname.lastname@example.org wrote:
> On Wed, 3 Oct 2001, Neil Brown wrote:
> > On Wednesday October 3, email@example.com wrote:
> > > 3) Rewrite to do I/O directly via pagecache?
> > 4) Rewrite to do I/O directly via generic_make_request just like it
> > does for all other I/O to underlying devices.
> > It is on my (mental) todo list, but doesn't have a high priority.
> > At the same time, it would be good to get write_disk_sb to notice
> > if the write failed.....
> Folks, there's a problem aside of set_blocksize(). You are doing memset
> and memcpy on unlocked buffer returned by getblk(). That's a race -
> if that buffer is currently being read into, we will get a random crap.
> And write it to disk afterwards.
> General rule: don't modify buffer you've got from getblk() unless you've
> locked it and mark it uptodate before you unlock. We had the same
> bug in ext2, BTW.
What I am saying is "don't use the buffer cache at all" or any cache.
Don't use getblk.
bh = kmalloc(sizeof(*bh));
bh->b_data = rdev->sb; /* it is always one page */
bh->b_rdev = rdev->dev;
bh->b_rsector = sb_offset*2;
bh->b_end_io = md_just_set_a_flag_and_call_wakeup;
bh->b_flags = 1<<B_Locked;
wait_disk_event((bh->b_flags & (1<<B_Locked)), bh->b_wait);
err = bh->b_flags & (1<<B_Uptodate);
with typos corrected and a fairly obvious definition of
fairly similar to end_buffer_io_sync.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/