From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Mickaël Salaün" <mic@digikod.net>,
linux-security-module@vger.kernel.org,
"Kees Cook" <kees@kernel.org>
Subject: Re: linux-next: Tree for May 16 (security/landlock/ruleset.c)
Date: Fri, 16 May 2025 19:54:14 -0700 [thread overview]
Message-ID: <e3754f69-1dea-4542-8de0-a567a14fb95b@infradead.org> (raw)
In-Reply-To: <20250516202417.31b13d13@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1023 bytes --]
On 5/16/25 3:24 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20250515:
>
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
[-- Attachment #2: config-r9208.gz --]
[-- Type: application/gzip, Size: 28788 bytes --]
next parent reply other threads:[~2025-05-17 2:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250516202417.31b13d13@canb.auug.org.au>
2025-05-17 2:54 ` Randy Dunlap [this message]
2025-05-19 15:29 ` linux-next: Tree for May 16 (security/landlock/ruleset.c) Mickaël Salaün
2025-05-19 18:19 ` Kees Cook
2025-05-19 18:41 ` Mickaël Salaün
2025-05-19 19:15 ` Kees Cook
2025-05-19 20:26 ` Randy Dunlap
2025-05-20 16:44 ` Kees Cook
2025-05-20 14:01 ` Andy Shevchenko
2025-05-20 16:47 ` Kees Cook
2025-05-20 14:45 ` Mickaël Salaün
2025-05-20 15:48 ` Randy Dunlap
2025-05-20 16:15 ` Kees Cook
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e3754f69-1dea-4542-8de0-a567a14fb95b@infradead.org \
--to=rdunlap@infradead.org \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mic@digikod.net \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).