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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080729123513.GG9378@mit.edu>
Date:	Tue, 29 Jul 2008 08:35:13 -0400
From:	Theodore Tso <tytso@....EDU>
To:	Hidehiro Kawai <hidehiro.kawai.ez@...achi.com>
Cc:	Ext4 Developers List <linux-ext4@...r.kernel.org>,
	sugita <yumiko.sugita.yf@...achi.com>,
	Satoshi OSHIMA <satoshi.oshima.fk@...achi.com>
Subject: Re: [PATCH] jbd2: don't abort if flushing file data failed

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html