Re: [PATCH] jbd2: don't abort if flushing file data failed

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Jul 29, 2008 at 02:53:36PM +0900, Hidehiro Kawai wrote:
> Hello, Ted
> 
> > [PATCH] ext4: don't read inode block if the buffer has a write error
> > [PATCH] jbd2: don't abort if flushing file data failed
> 
> Thank you for porting my ext3/jbd patches to ext4/jbd2.
> I would appreciate if you port the remained two patch set (haven't
> been posted yet), too.  Although I'll try to port them by myself. 

If they are the ones which I think you are referring to, I don't
believe they apply to ext4 since we are now using the
generic_writepages routines to flush data pages to disk during a
journal commit.  I've checked those code paths, and I believe they do
set AS_EIO correctly; I would appreciate it though if you could double
check to make sure they are do everything that needs to be done to
handle write errors correctly.

Thanks, regards,

						- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Reiser Filesystem Development]     [Ceph FS]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite National Park]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]     [Linux Media]

  Powered by Linux