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: <20130128144528.GF22711@thunk.org> Date: Mon, 28 Jan 2013 09:45:28 -0500 From: Theodore Ts'o <tytso@....edu> To: Jan Kara <jack@...e.cz> Cc: linux-ext4@...r.kernel.org Subject: Re: [PATCH 06/12] ext4: Move work from io_end to inode On Fri, Jan 18, 2013 at 01:00:40PM +0100, Jan Kara wrote: > It does not make much sense to have struct work in ext4_io_end_t because we > always use it for only one ext4_io_end_t per inode (the first one in the > i_completed_io list). So just move the structure to inode itself. This also > allows for a small simplification in processing io_end structures. > > Signed-off-by: Jan Kara <jack@...e.cz> Thanks, applied. (Note, I haven't applied patch 5 yet because it has a dependency on patch #4, and I'm waiting to hear whether we should apply this given the race condition which Dmitry has found. It sounds like it's a pre-existing condition, and not a regression, but I want get a confirmation that applying patches 5 and 6 won't make things worse...) - Ted -- 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