Re: [PATCH] Fix ext2 error reporting on fsync

[Jan Kara <jack@suse.cz>]

> On Thursday 12 January 2006 06:52, Andrew Morton 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.
> 
> Hmmm, how does this work with two concurrent fsyncs on different files?
  Where is the problem? Different files will have different buffers in
its private_list lists, different address_space structures etc. So they
should not interact in any way. Or am I missing something?

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