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: Wed, 7 Sep 2022 15:30:16 -0700 From: Andrew Morton <akpm@...ux-foundation.org> To: Davidlohr Bueso <dave@...olabs.net> Cc: dan.j.williams@...el.com, x86@...nel.org, nvdimm@...ts.linux.dev, linux-cxl@...r.kernel.org, peterz@...radead.org, bp@...en8.de, dave.jiang@...el.com, Jonathan.Cameron@...wei.com, vishal.l.verma@...el.com, ira.weiny@...el.com, a.manzanares@...sung.com, linux-kernel@...r.kernel.org Subject: Re: [PATCH -next] memregion: Add arch_flush_memregion() interface I really dislike the term "flush". Sometimes it means writeback, sometimes it means invalidate. Perhaps at other times it means both. Can we please be very clear in comments and changelogs about exactly what this "flush" does. With bonus points for being more specific in the function naming?
Powered by blists - more mailing lists