| 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: <20141030014405.GE5000@thunk.org> Date: Wed, 29 Oct 2014 21:44:06 -0400 From: Theodore Ts'o <tytso@....edu> To: Chris Friesen <chris.friesen@...driver.com> Cc: Thomas Gleixner <tglx@...utronix.de>, Austin Schuh <austin@...oton-tech.com>, pavel@...linux.ru, "J. Bruce Fields" <bfields@...ldses.org>, linux-ext4@...r.kernel.org, adilger.kernel@...ger.ca, rt-users <linux-rt-users@...r.kernel.org> Subject: Re: RT/ext4/jbd2 circular dependency On Wed, Oct 29, 2014 at 05:37:03PM -0600, Chris Friesen wrote: > > 1) Is this something that could hit mainline as well, or just the RT kernel? Yes, it could hit the mainline as well. It's more about the workload and how the files are written to and/or sync'ed. > 2) If it can hit mainline, is this something that should be considered for > the various longterm-support kernels? (3.10, maybe 3.4) Yes, probably. > 3) For 3.4, do you think that it's sufficient to backport the three commits > I mentioned, or are you aware of others that I should be looking at as well? No, those three commits would be quite sufficient. If you could handle doing the backports, I would greatly appreciate it! Sounds like you've done so for 3.4 already, and it should be fairly straightforward to get them into 3.10, since b34090e landed in 3.11. Thanks, - 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