From: Andrew Morton <akpm@zip.com.au>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Alexander Viro <viro@math.psu.edu>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [patch] truncate fixes
Date: Sun, 06 Jan 2002 19:48:38 -0800 [thread overview]
Message-ID: <3C391A96.63FDBA8@zip.com.au> (raw)
In-Reply-To: <3C36DEA9.AEA2A402@zip.com.au>, <3C36DEA9.AEA2A402@zip.com.au>; from akpm@zip.com.au on Sat, Jan 05, 2002 at 03:08:25AM -0800 <20020107043236.J1561@athlon.random>
Andrea Arcangeli wrote:
>
> On Sat, Jan 05, 2002 at 03:08:25AM -0800, Andrew Morton wrote:
> > }
> > return 0;
> > out:
> > + bh = head;
> > + block_start = 0;
> > + do {
> > + if (buffer_new(bh) && !buffer_uptodate(bh)) {
> > + memset(kaddr+block_start, 0, bh->b_size);
> > + set_bit(BH_Uptodate, &bh->b_state);
> > + mark_buffer_dirty(bh);
> > + }
> > + block_start += bh->b_size;
> > + bh = bh->b_this_page;
> > + } while (bh != head);
> > return err;
> > }
>
> the above code will end marking uptodate (zeroed) buffers relative to
> blocks that cannot be read from disk. So a read-retry won't hit the disk
> and that's wrong.
>
> I think that will be fixed by additionally also return -EIO in the
> wait_on_buffer loop (instead of goto out), so we won't generate zeroed
> uptodate cache in case of read failure.
>
Right. There's also the case where get_block() returns -EIO when,
for example, it fails on reading an indirect block. We end up
writing zeroes into some of the blocks. But I think that behaviour
is correct.
(I think I'll add a buffer_mapped() test to this code as well. It's
a bit redundant because the fs shouldn't go setting BH_New and not
BH_Mapped, but this code is _very_ rarely executed, and I haven't
tested all filesystems...)
@@ -1633,12 +1660,22 @@ static int __block_prepare_write(struct
*/
while(wait_bh > wait) {
wait_on_buffer(*--wait_bh);
- err = -EIO;
if (!buffer_uptodate(*wait_bh))
- goto out;
+ return -EIO;
}
return 0;
out:
+ bh = head;
+ block_start = 0;
+ do {
+ if (buffer_new(bh) && buffer_mapped(bh) && !buffer_uptodate(bh)) {
+ memset(kaddr+block_start, 0, bh->b_size);
+ set_bit(BH_Uptodate, &bh->b_state);
+ mark_buffer_dirty(bh);
+ }
+ block_start += bh->b_size;
+ bh = bh->b_this_page;
+ } while (bh != head);
return err;
}
I'll retest this, including the -EIO path.
next prev parent reply other threads:[~2002-01-07 3:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-05 11:08 [patch] truncate fixes Andrew Morton
2002-01-07 2:46 ` Andrea Arcangeli
2002-01-07 2:53 ` Andrew Morton
2002-01-07 3:16 ` Andrea Arcangeli
2002-01-07 5:24 ` Alexander Viro
2002-01-07 3:11 ` Andrew Morton
2002-01-07 3:58 ` Andrea Arcangeli
2002-01-07 3:32 ` Andrea Arcangeli
2002-01-07 3:48 ` Andrew Morton [this message]
2002-01-07 4:12 ` Andrea Arcangeli
2002-01-07 4:28 ` Andrew Morton
2002-01-07 5:09 ` Andrea Arcangeli
2002-01-07 12:41 ` Daniel Phillips
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=3C391A96.63FDBA8@zip.com.au \
--to=akpm@zip.com.au \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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.