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: <e475a747-2f33-4c43-b6bd-98df2e57099a@phunq.net> Date: Sat, 21 Jun 2014 20:32:03 -0700 From: Daniel Phillips <daniel@...nq.net> To: James Bottomley <James.Bottomley@...senpartnership.com> Cc: Lukáš Czerner <lczerner@...hat.com>, Pavel Machek <pavel@....cz>, Dave Chinner <david@...morbit.com>, <linux-kernel@...r.kernel.org>, <linux-fsdevel@...r.kernel.org>, Linus Torvalds <torvalds@...ux-foundation.org>, Andrew Morton <akpm@...ux-foundation.org> Subject: Re: [RFC] Tux3 for review On Saturday, June 21, 2014 12:29:01 PM PDT, James Bottomley wrote: > On Thu, 2014-06-19 at 14:58 -0700, Daniel Phillips wrote: >> We already removed 450 lines of core kernel workarounds from Tux3 with an >> approach that was literally cut and pasted from one of Dave's >> emails. Then >> Dave changed his mind. Now the Tux3 team has been assigned a research >> project to improve core kernel writeback instead of simply adapting the >> approach that is already proven to work well enough. That is a rather >> blatant example of "perfect is the enemy of good enough". Please read the >> thread. > > That's a bit disingenuous: the concern has always been how page forking > interacted with writeback. It's not new, it was one of the major things > brought up at LSF 14 months ago, so you weren't just assigned this. [citation needed] Regards, Daniel -- 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