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: <20130214213250.GA4887@quack.suse.cz> Date: Thu, 14 Feb 2013 22:32:50 +0100 From: Jan Kara <jack@...e.cz> To: Theodore Ts'o <tytso@....edu> Cc: Jan Kara <jack@...e.cz>, Dmitry Monakhov <dmonakhov@...nvz.org>, linux-ext4@...r.kernel.org Subject: Re: REGRESSION: [PATCH 04/12] ext4: Disable merging of uninitialized extents On Thu 14-02-13 14:05:55, Ted Tso wrote: > On Thu, Feb 14, 2013 at 05:11:16PM +0100, Jan Kara wrote: > > OK, so I've debugged this. It wasn't actually that hard. The problem is > > that mpage_da_map_and_submit() prepares extent with e.g. 256 blocks but > > later we submit a shorter bio e.g. because it cannot carry that many pages. > > So ->end_io is called only for first 128 blocks or so. I spotted this > > problem already before, just it didn't come up when Ted sent me this bug > > report. > > So can we get a corruption without these patches, but it was a lot > harder to hit that case before? When the bio is shorter we just need to split the unwritten extent when processing end_io callback. That is properly handled after Dmitry's fixes so corruption can happen only when we are close to ENOSPC and the split fails. Now we started seeing the split is happening because one of the patches added the warning that the split from end_io is happening... 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