linux-next: Tree for May 16 (security/landlock/ruleset.c)
Mickaël Salaün
mic at digikod.net
Mon May 19 15:29:30 UTC 2025
On Fri, May 16, 2025 at 07:54:14PM -0700, Randy Dunlap wrote:
>
>
> On 5/16/25 3:24 AM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20250515:
Thanks for the report.
It is the same warning as reported here:
https://lore.kernel.org/all/202501040747.S3LYfvYq-lkp@intel.com/
I don't know what the actual issue is though.
>
> on i386:
>
> In file included from ../arch/x86/include/asm/string.h:3,
> from ../include/linux/string.h:65,
> from ../include/linux/bitmap.h:13,
> from ../include/linux/cpumask.h:12,
> from ../include/linux/smp.h:13,
> from ../include/linux/lockdep.h:14,
> from ../security/landlock/ruleset.c:16:
> ../security/landlock/ruleset.c: In function 'create_rule':
> ../arch/x86/include/asm/string_32.h:150:25: warning: '__builtin_memcpy' accessing 4294967295 bytes at offsets 20 and 0 overlaps 6442450943 bytes at offset -2147483648 [-Wrestrict]
> 150 | #define memcpy(t, f, n) __builtin_memcpy(t, f, n)
> | ^~~~~~~~~~~~~~~~~~~~~~~~~
> ../security/landlock/ruleset.c:137:9: note: in expansion of macro 'memcpy'
> 137 | memcpy(new_rule->layers, layers,
> | ^~~~~~
>
>
> Full randconfig file is attached.
>
> --
> ~Randy
More information about the Linux-security-module-archive
mailing list