public inbox for [email protected]
 help / color / mirror / Atom feed
From: Marco Elver <[email protected]>
To: [email protected]
Cc: kernel test robot <[email protected]>,
	Frederic Weisbecker <[email protected]>,
	[email protected],
	 "GNU/Weeb Mailing List" <[email protected]>,
	[email protected], [email protected]
Subject: Re: [ammarfaizi2-block:paulmck/linux-rcu/pmladek.2022.06.15a 133/140] vmlinux.o: warning: objtool: __ct_user_exit+0x41: call to __kasan_check_read() leaves .noinstr.text section
Date: Thu, 16 Jun 2022 10:19:18 +0200	[thread overview]
Message-ID: <CANpmjNMswUJhqfttxZGbkfN7X5d5FLiS1yPXzzGDivLtWDB9=g@mail.gmail.com> (raw)
In-Reply-To: <20220615211717.GA972937@paulmck-ThinkPad-P17-Gen-1>

On Wed, 15 Jun 2022 at 23:17, Paul E. McKenney <[email protected]> wrote:
>
> On Wed, Jun 15, 2022 at 01:40:39PM -0700, Paul E. McKenney wrote:
> > On Thu, Jun 16, 2022 at 04:26:16AM +0800, kernel test robot wrote:
> > > tree:   https://github.com/ammarfaizi2/linux-block paulmck/linux-rcu/pmladek.2022.06.15a
> > > head:   0ba7324b44282870af740a5a121add62c7f5f730
> > > commit: db21b02f8044e812f8a5e3811f602409290e3ede [133/140] context_tracking: Convert state to atomic_t
> > > config: x86_64-randconfig-r003-20220516 (https://download.01.org/0day-ci/archive/20220616/[email protected]/config)
> > > compiler: gcc-11 (Debian 11.3.0-3) 11.3.0
> > > reproduce (this is a W=1 build):
> > >         # https://github.com/ammarfaizi2/linux-block/commit/db21b02f8044e812f8a5e3811f602409290e3ede
> > >         git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
> > >         git fetch --no-tags ammarfaizi2-block paulmck/linux-rcu/pmladek.2022.06.15a
> > >         git checkout db21b02f8044e812f8a5e3811f602409290e3ede
> > >         # save the config file
> > >         mkdir build_dir && cp config build_dir/.config
> > >         make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash
> > >
> > > If you fix the issue, kindly add following tag where applicable
> > > Reported-by: kernel test robot <[email protected]>
> > >
> > > All warnings (new ones prefixed by >>):
> > >
> > > >> vmlinux.o: warning: objtool: __ct_user_exit+0x41: call to __kasan_check_read() leaves .noinstr.text section
> > > >> vmlinux.o: warning: objtool: __ct_user_enter+0x7f: call to __kasan_check_read() leaves .noinstr.text section
> >
> > Marco, Dmitry, my guess is that this is due to the ct->active check in
> > both functions.  Are we supposed to do something to make this sort of
> > thing safe for KASAN?
>
> This time actually CCing Marco and Dmitry...

It's due to the atomic_read()s within the noinstr function. Within
noinstr you can use arch_atomic_read() to avoid the instrumentation.

Thanks,
-- Marco

  reply	other threads:[~2022-06-16  8:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-15 20:26 [ammarfaizi2-block:paulmck/linux-rcu/pmladek.2022.06.15a 133/140] vmlinux.o: warning: objtool: __ct_user_exit+0x41: call to __kasan_check_read() leaves .noinstr.text section kernel test robot
2022-06-15 20:40 ` Paul E. McKenney
2022-06-15 21:17   ` Paul E. McKenney
2022-06-16  8:19     ` Marco Elver [this message]
2022-06-16 13:40       ` Paul E. McKenney
2022-06-16 16:44         ` Paul E. McKenney
2022-06-16 17:32           ` Marco Elver
2022-06-16 17:49             ` Paul E. McKenney

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='CANpmjNMswUJhqfttxZGbkfN7X5d5FLiS1yPXzzGDivLtWDB9=g@mail.gmail.com' \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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