| 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
| ||
|
Message-ID: <20130513170124.GJ400@quack.suse.cz> Date: Mon, 13 May 2013 19:01:24 +0200 From: Jan Kara <jack@...e.cz> To: Eric Sandeen <sandeen@...hat.com> Cc: Dmitry Monakhov <dmonakhov@...nvz.org>, Theodore Ts'o <tytso@....edu>, EUNBONG SONG <eunb.song@...sung.com>, Jan Kara <jack@...e.cz>, "linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, linux-xfs@...r.kernel.org, Dave Chinner <david@...morbit.com> Subject: Re: EXT4 regression caused 4eec7 On Mon 13-05-13 11:34:12, Eric Sandeen wrote: > On 5/12/13 4:01 AM, Dmitry Monakhov wrote: > > In fact '4eec70' are vexing because I have reviewed and tested this patch before > > it was marked as Review-by, but missed the bug. This is because xfstests > > was executed manually logs was full of warnings but tainted flag was not > > checked at the end. > > Can you elaborate on this? What was logged, and is it something we could > try to pick up post-test in xfstests? Generally I think it might be useful if xfstests would fail / warn if kernel became tainted during the test (e.g. due to WARN_ON or oops, or something like that). It should be even relatively easy to implement (just compare /proc/sys/kernel/tainted before and after each test). Honza -- Jan Kara <jack@...e.cz> SUSE Labs, CR -- 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