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: <CABi2SkWU6orm-wBFKVt9rsSpYURHPb7fjHRzkOiPGd=Lh-DdkA@mail.gmail.com> Date: Mon, 17 Mar 2025 11:14:36 -0700 From: Jeff Xu <jeffxu@...omium.org> To: Geert Uytterhoeven <geert@...ux-m68k.org> Cc: Lorenzo Stoakes <lorenzo.stoakes@...cle.com>, akpm@...ux-foundation.org, Liam.Howlett@...cle.com, agordeev@...ux.ibm.com, borntraeger@...ux.ibm.com, gor@...ux.ibm.com, hca@...ux.ibm.com, kees@...nel.org, linux-hardening@...r.kernel.org, linux-kernel@...r.kernel.org, linux-mm@...ck.org, svens@...ux.ibm.com, thomas.weissschuh@...utronix.de Subject: Re: [PATCH] mseal sysmap: add arch-support txt On Fri, Mar 14, 2025 at 3:41 AM Geert Uytterhoeven <geert@...ux-m68k.org> wrote: > > Hi Jeff, > > On Thu, 13 Mar 2025 at 23:26, Jeff Xu <jeffxu@...omium.org> wrote: > > On Wed, Mar 12, 2025 at 10:21 PM Lorenzo Stoakes > > <lorenzo.stoakes@...cle.com> wrote: > > > On Thu, Mar 13, 2025 at 12:06:23AM +0000, jeffxu@...omium.org wrote: > > > > From: Jeff Xu <jeffxu@...omium.org> > > > > Add Documentation/features/core/mseal_sys_mappings/arch-support.txt > > > > > > > > Signed-off-by: Jeff Xu <jeffxu@...omium.org> > > Thanks for your patch! > > > > > --- /dev/null > > > > +++ b/Documentation/features/core/mseal_sys_mappings/arch-support.txt > > > > @@ -0,0 +1,30 @@ > > > > +# > > > > +# Feature name: mseal-system-mappings > > > > +# Kconfig: ARCH_SUPPORTS_MSEAL_SYSTEM_MAPPINGS > > > > +# description: arch supports mseal system mappings > > > > +# > > > > + ----------------------- > > > > + | arch |status| > > > > + ----------------------- > > > > + | alpha: | TODO | > > > > + | arc: | TODO | > > > > + | arm: | N/A | > > > > + | arm64: | ok | > > > > + | csky: | TODO | > > > > + | hexagon: | TODO | > > > > + | loongarch: | TODO | > > > > + | m68k: | TODO | > > > > + | microblaze: | TODO | > > > > + | mips: | TODO | > > > > + | nios2: | TODO | > > > > + | openrisc: | TODO | > > > > + | parisc: | TODO | > > > > + | powerpc: | TODO | > > > > + | riscv: | TODO | > > > > + | s390: | ok | > > > > + | sh: | TODO | > > > > + | sparc: | TODO | > > > > + | um: | TODO | > > > > + | x86: | ok | > > > > + | xtensa: | TODO | > > > > + ----------------------- > > > > Plus I feel this need expansion a bit 'N/A' is because of being non-64 bit > > > right? > > > > > Below is the definition of N/A in Documentation/features/arch-support.txt > > | N/A| # feature doesn't apply to the architecture > > > > It fits the arm case because mseal is not supported in 32 bit. > > IIUIC, you can already s@...O@N/A@ for all other 32-bit architectures, > so we don't accidentally spend time on looking into adding the support? > Sure, my architecture knowledge is limited. I just checked this, it seems to me that csky, m68k, nios2, sh, xtensa doesn't have 64 bits support, the rest have 64 bits. Is this correct ? Thanks -Jeff > Gr{oetje,eeting}s, > > Geert > > -- > Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org > > In personal conversations with technical people, I call myself a hacker. But > when I'm talking to journalists I just say "programmer" or something like that. > -- Linus Torvalds
Powered by blists - more mailing lists