linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Andrew Morton <akpm@osdl.org>
Cc: Chris Mason <mason@suse.com>, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] Fix ext2 error reporting on fsync
Date: Wed, 18 Jan 2006 23:46:53 +0100	[thread overview]
Message-ID: <20060118224652.GA6434@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <20060112181628.63c4bf39.akpm@osdl.org>

> Chris Mason <mason@suse.com> wrote:
> >
> > On Thursday 12 January 2006 15:47, Andrew Morton wrote:
> > > Jan Kara <jack@suse.cz> wrote:
> > > > > Jan Kara <jack@suse.cz> wrote:
> > > > >
> > > > > hm, yes, try_to_free_buffers() against a blockdev page is a problem. 
> > > > > But I think it's fixable.
> > > > >
> > > > > In the second loop of drop_buffers(), if we find a bh which had a write
> > > > > error we need to set AS_EIO on the address_space which is interested in
> > > > > this buffer.
> > > > >
> > > > > That address_space is pinned by a) the fact that it has buffers at
> > > > > ->private_list and b) we hold the blockdev mapping's private_lock.
> > > > >
> > > > > The only problem is actually _finding_ the address_space which is
> > > > > interested in this buffer_head.  Looks like we'd need a backpointer in
> > > > > the buffer_head.
> > > >
> > > >   Yes, the pointer seems to be inevitable in this solution. If you think
> > > > the improvement is worth adding 4 bytes to each buffer_head, then I can
> > > > write the patch.
> > >
> > > hm.  It only affects what are now rarely-used filesystems like ext2, minix,
> > > etc.  Not sure about reiser3.  But it is a strict correctness issue.  I
> > > suppose we should do it.  It'd be nice to find a way to avoid increasing
> > > the bh size..
> > >
> > 
> > I know my patch is pretty nasty, but is it really worth adding complexity to 
> > the base code for this corner case?
> > 
> 
> It's not much complexity: a few set_bits and test_and_clear_bits in three
> places.  The main drawback is a larger buffer_head.
> 
> Yeah, it's a pita, but it is a data-integrity correctness thing.
  There's a way to avoid the extra pointer in buffer_head: we could
change the circular linked list b_assoc_buffers to a non-circular one
(probably use hlists). Then if we find a buffer with IO error, we could
find a list head and from it compute the pointer to the mapping... It
would not be fast but on IO error I think we could afford it. Do you think
it's a good idea?

									Honza
-- 
Jan Kara <jack@suse.cz>
SuSE CR Labs

  reply	other threads:[~2006-01-18 22:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-11 17:43 [PATCH] Fix ext2 error reporting on fsync Jan Kara
2006-01-12  4:24 ` Andrew Morton
2006-01-12 10:20   ` Jan Kara
2006-01-12 11:52     ` Andrew Morton
2006-01-12 13:58       ` Chris Mason
2006-01-12 14:21         ` Jan Kara
2006-01-12 15:36           ` Chris Mason
2006-01-12 16:32             ` Jan Kara
2006-01-12 14:26       ` Jan Kara
2006-01-12 20:47         ` Andrew Morton
2006-01-13  2:08           ` Chris Mason
2006-01-13  2:16             ` Andrew Morton
2006-01-18 22:46               ` Jan Kara [this message]
2006-01-18 23:06                 ` Andrew Morton
2006-01-19 12:21                   ` Jan Kara
2006-01-19 21:16                     ` Andrew Morton
2006-01-20 13:41                       ` Jan Kara
2006-01-20 21:24                         ` Andrew Morton
2006-01-20 21:31                           ` Andrew Morton
2006-01-20 21:33                             ` Andrew Morton
2006-01-22 22:55                             ` Jan Kara
2006-01-23  0:06                               ` Andrew Morton
2006-01-22 22:32                           ` Jan Kara
2006-01-22 23:31                           ` Jan Kara

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=20060118224652.GA6434@atrey.karlin.mff.cuni.cz \
    --to=jack@suse.cz \
    --cc=akpm@osdl.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=mason@suse.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).