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]
Date:	Tue, 21 Oct 2008 15:24:47 +0900
From:	Hidehiro Kawai <hidehiro.kawai.ez@...achi.com>
To:	Theodore Tso <tytso@....edu>,
	Andrew Morton <akpm@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org, linux-ext4@...r.kernel.org,
	adilger@....com, jack@...e.cz, sandeen@...hat.com
Subject: Re: status of the ext3/jbd error handling enhancement patches

Theodore Tso wrote:

> On Sun, Oct 19, 2008 at 10:13:31PM -0700, Andrew Morton wrote:
> 
>>>  #jbd-fix-error-handling-for-checkpoint-io.patch: double-check this
>>>  jbd-fix-error-handling-for-checkpoint-io.patch
>>>  ext3-add-checks-for-errors-from-jbd.patch
>>>  jbd-test-bh_write_eio-to-detect-errors-on-metadata-buffers.patch
>>>
>>>They improve filesystem corruption problem and it is needed by
>>>mission critical systems.
>>>
>>>Could you tell me what is your concern (you commented, "double-check
>>>this") ?  Are there something that I can help?  For example, I can
>>>provide some SystemTap scripts to help tests.
>>
>>I forget my reasons for that - would need to go back and review the
>>discussions when the patch was first merged.
>>
>>One of the above patches (I forget which) breaks the build because it
>>expects the presence of Al Viro's VFS tree, and that hasn't been merged
>>yet.  I need to wait and see if that merge will be happening (seems
>>unlikely) and if not, rework the patch against mainline.

I see.  Thank you for your work.

> Strange; I don't recall any of the ext4 variants of the error handling
> patches requiring Al's VFS tree.  And I thought all of them have been
> merged into Linus's tree at this point.

I checked Al's VFS tree and I found commit
6ac465f99b29f74ca5a62bc32a8772985d9a071b changes codes near where
one of my patch changes (in ext3/ext4_quota_on()), but not the same code.

> Kawai-san, could you double check and see if I processed all of your
> patches and pushed them to Linus?  I was pretty sure I had...

I confirmed that all of my ext4/jbd2 patches have been merged into
mainline.  Thank you very much!

Regards,
-- 
Hidehiro Kawai
Hitachi, Systems Development Laboratory
Linux Technology Center

--
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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ