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: <ce82a562db208250526f21a21e54bfc5b85f167a.camel@intel.com> Date: Thu, 5 Oct 2023 18:11:49 +0000 From: "Edgecombe, Rick P" <rick.p.edgecombe@...el.com> To: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "rppt@...nel.org" <rppt@...nel.org> CC: "tglx@...utronix.de" <tglx@...utronix.de>, "deller@....de" <deller@....de>, "mcgrof@...nel.org" <mcgrof@...nel.org>, "bjorn@...nel.org" <bjorn@...nel.org>, "davem@...emloft.net" <davem@...emloft.net>, "nadav.amit@...il.com" <nadav.amit@...il.com>, "linux@...linux.org.uk" <linux@...linux.org.uk>, "netdev@...r.kernel.org" <netdev@...r.kernel.org>, "linux-mips@...r.kernel.org" <linux-mips@...r.kernel.org>, "linux-riscv@...ts.infradead.org" <linux-riscv@...ts.infradead.org>, "hca@...ux.ibm.com" <hca@...ux.ibm.com>, "catalin.marinas@....com" <catalin.marinas@....com>, "kent.overstreet@...ux.dev" <kent.overstreet@...ux.dev>, "puranjay12@...il.com" <puranjay12@...il.com>, "palmer@...belt.com" <palmer@...belt.com>, "linux-s390@...r.kernel.org" <linux-s390@...r.kernel.org>, "chenhuacai@...nel.org" <chenhuacai@...nel.org>, "tsbogend@...ha.franken.de" <tsbogend@...ha.franken.de>, "linux-trace-kernel@...r.kernel.org" <linux-trace-kernel@...r.kernel.org>, "mpe@...erman.id.au" <mpe@...erman.id.au>, "linux-parisc@...r.kernel.org" <linux-parisc@...r.kernel.org>, "x86@...nel.org" <x86@...nel.org>, "mark.rutland@....com" <mark.rutland@....com>, "christophe.leroy@...roup.eu" <christophe.leroy@...roup.eu>, "linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>, "rostedt@...dmis.org" <rostedt@...dmis.org>, "will@...nel.org" <will@...nel.org>, "dinguyen@...nel.org" <dinguyen@...nel.org>, "naveen.n.rao@...ux.ibm.com" <naveen.n.rao@...ux.ibm.com>, "sparclinux@...r.kernel.org" <sparclinux@...r.kernel.org>, "linux-modules@...r.kernel.org" <linux-modules@...r.kernel.org>, "bpf@...r.kernel.org" <bpf@...r.kernel.org>, "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>, "song@...nel.org" <song@...nel.org>, "linux-mm@...ck.org" <linux-mm@...ck.org>, "loongarch@...ts.linux.dev" <loongarch@...ts.linux.dev>, "akpm@...ux-foundation.org" <akpm@...ux-foundation.org> Subject: Re: [PATCH v3 03/13] mm/execmem, arch: convert simple overrides of module_alloc to execmem On Mon, 2023-09-18 at 10:29 +0300, Mike Rapoport wrote: > +/** > + * struct execmem_range - definition of a memory range suitable for > code and > + * related data allocations > + * @start: address space start > + * @end: address space end (inclusive) > + * @pgprot: permissions for memory in this address space > + * @alignment: alignment required for text allocations > + */ > +struct execmem_range { > + unsigned long start; > + unsigned long end; > + pgprot_t pgprot; > + unsigned int alignment; > +}; Not a strong opinion, but range doesn't seem an appropriate name. It *has* a range, but also other allocation configuration. It gets especially confusing when multiple "ranges" have the same range. Maybe execmem_alloc_params?
Powered by blists - more mailing lists