linux-kernel - Re: status of the ext3/jbd error handling enhancement patches

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] [day] [month] [year] [list]

Message-Id: <20081020233726.5682a278.akpm@linux-foundation.org>
Date:	Mon, 20 Oct 2008 23:37:26 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Hidehiro Kawai <hidehiro.kawai.ez@...achi.com>
Cc:	Theodore Tso <tytso@....edu>, 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

On Tue, 21 Oct 2008 15:24:47 +0900 Hidehiro Kawai <hidehiro.kawai.ez@...achi.com> wrote:

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

OK.

Don't worry about it - I'll fix things up some time this week.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/