From: "Paul E. McKenney" <paulmck@kernel.org>
To: jpoimboe@kernel.org, peterz@infradead.org
Cc: linux-kernel@vger.kernel.org, sfr@canb.auug.org.au
Subject: objtool warning from next-20230125
Date: Thu, 26 Jan 2023 10:23:02 -0800 [thread overview]
Message-ID: <20230126182302.GA687063@paulmck-ThinkPad-P17-Gen-1> (raw)
Hello!
I have started seeing these objtool warnings from a wide variety of
KASAN-enabled rcutorture-related test scenarios in next-20230125. It has
been awhile since I tested -next, so I am not yet sure where this started.
vmlinux.o: warning: objtool: __asan_memset+0x34: call to __memset() with UACCESS enabled
vmlinux.o: warning: objtool: __asan_memmove+0x4d: call to __memmove() with UACCESS enabled
vmlinux.o: warning: objtool: __asan_memcpy+0x4d: call to __memcpy() with UACCESS enabled
As usual, should I be worried?
Thanx, Paul
next reply other threads:[~2023-01-26 18:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 18:23 Paul E. McKenney [this message]
2023-01-26 20:59 ` Josh Poimboeuf
2023-01-26 23:20 ` Paul E. McKenney
2023-01-27 12:14 ` Peter Zijlstra
2023-01-27 19:37 ` Paul E. McKenney
2023-02-11 10:30 ` [tip: sched/core] objtool: mem*() are not uaccess safe tip-bot2 for Peter Zijlstra
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=20230126182302.GA687063@paulmck-ThinkPad-P17-Gen-1 \
--to=paulmck@kernel.org \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--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
all inboxes | Powered by JetHome®