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
| ||
|
Date: Tue, 9 Jun 2009 01:50:49 +0530 From: "Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com> To: Theodore Tso <tytso@....edu> Cc: cmm@...ibm.com, sandeen@...hat.com, linux-ext4@...r.kernel.org, Jan Kara <jack@...e.cz> Subject: Re: [PATCH -V2 2/2] ext4: truncate the file properly if we fail to copy data from userspace On Mon, Jun 08, 2009 at 03:14:20PM -0400, Theodore Tso wrote: > On Mon, Jun 08, 2009 at 10:13:57PM +0530, Aneesh Kumar K.V wrote: > > I think i both the case Jan's patch > > allocate-blocks-correctly-with-subpage-blocksize need an update ? Since you have put > > the patch before Jan's changes. > > OK, here's how I updated Jan's patch. I'm going to assume that we'll > submit the ext4 patch queue immediately as soon as the merge window > opens, since my impression is Jan is still waiting for some mm > developers to review his patch set. > > Annesh, does this look good to you? I just did a quick look. Should we do a block_unlock_hole_extend after journal_stop. We do a block_lock_hole_extend before journal_start. > > Jan, if we go down this path, you'll need to update your ext4 patch > with this updated one, to take into account the changes from Aneesh's > patch. > > (We could do it the other way, but that means even more patches queued > up behind Jan's patch series, and I didn't realize originally that > Aneesh intended for these to be queued after Jan's patches. So it > seemed easier to just order Aneesh's patches to avoid block allocation > leaks first, since they are at least functionally (if not > syntactically) independent of the subpagesize blocksize patches.) -aneesh -- 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