| 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: Mon, 10 Dec 2007 05:43:45 -0800 From: Daniel Phillips <phillips@...nq.net> To: Jens Axboe <jens.axboe@...cle.com> Cc: linux-kernel@...r.kernel.org, Andrew Morton <akpm@...ux-foundation.org>, Peter Zijlstra <peterz@...radead.org> Subject: Re: [RFC] [PATCH] A clean aEvgeniy pproach to writeout throttling On Monday 10 December 2007 05:30, Jens Axboe wrote: > On Mon, Dec 10 2007, Daniel Phillips wrote: > "Let me close with perhaps the most relevant remarks: the attached > code has been in heavy testing and in production for months now. > Thus there is nothing theoretical when I say it works, and the patch > speaks for itself in terms of obvious correctness." That is quite correct, even without the redirect the code passed all our tests. Remember, we were testing for deadlock, not every possible block IO configuration. > We must have differing opinions on what obvious correctness is. Yes we do. You appear to have missed the plot entirely. I suppose I should remind you: this is about deadlock in _your_ subsystem that has been creating bug reports for years. Block writeout deadlock. Caused by a deficiency in _your_ subsystem. Got a plan? Or does endless, pointless flaming feel more like progress to you? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists