| 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: <Pine.LNX.4.64.0811150914080.16789@blonde.site> Date: Sat, 15 Nov 2008 09:28:37 +0000 (GMT) From: Hugh Dickins <hugh@...itas.com> To: Andrew Morton <akpm@...ux-foundation.org> cc: Jeremy Fitzhardinge <jeremy@...p.org>, Nick Piggin <nickpiggin@...oo.com.au>, Linux Memory Management List <linux-mm@...ck.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, "Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com>, Johannes Weiner <hannes@...xchg.org> Subject: Re: [PATCH 1/2] mm: implement remap_pfn_range with apply_to_page_range On Fri, 14 Nov 2008, Jeremy Fitzhardinge wrote: > Nick Piggin wrote: > > No, adding a cycle here or an indirect function call there IMO is > > not acceptable in core mm/ code without a good reason. > > <shrug> OK. I'm with Nick on this: admittedly remap_pfn_range() is a borderline case (since it has no latency breaks at present), but it is a core mm function, and I'd prefer we leave it as is unless good reason. So, no hurry, but I'd prefer mm-implement-remap_pfn_range-with-apply_to_page_range.patch mm-remap_pfn_range-restore-missing-flush.patch to be removed from mmotm - and don't I deserve that, just for actually reading the mm-commits boilerplate ;-? Hugh -- 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