mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rong Chen <rong.a.chen@intel.com>
To: Marco Elver <elver@google.com>, kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	"Paul E. McKenney" <paulmck@kernel.org>
Subject: Re: [kbuild-all] Re: [paulmck-rcu:dev.2021.12.02a 31/43] include/asm-generic/barrier.h:70:30: warning: 'kcsan_rmb' is static but used in inline function 'pte_offset_kernel' which is not static
Date: Tue, 7 Dec 2021 08:32:26 +0800	[thread overview]
Message-ID: <78e4a2b0-af5c-d13c-ef33-878f84555b36@intel.com> (raw)
In-Reply-To: <CANpmjNOpoYrgk85hsOroh67TqUPtawWCnbk1GwqdUnGEKrOP+w@mail.gmail.com>



On 12/4/21 21:02, Marco Elver wrote:
> On Sat, 4 Dec 2021 at 06:33, kernel test robot <lkp@intel.com> wrote:
> [...]
>>>> include/asm-generic/barrier.h:70:30: warning: 'kcsan_rmb' is static but used in inline function 'pte_offset_kernel' which is not static
>>        70 | #define smp_rmb()       do { kcsan_rmb(); __smp_rmb(); } while (0)
>>           |                              ^~~~~~~~~
>>     arch/alpha/include/asm/pgtable.h:303:9: note: in expansion of macro 'smp_rmb'
>>       303 |         smp_rmb(); /* see above */
>>           |         ^~~~~~~
>>>> include/asm-generic/barrier.h:70:30: warning: 'kcsan_rmb' is static but used in inline function 'pmd_offset' which is not static
>>        70 | #define smp_rmb()       do { kcsan_rmb(); __smp_rmb(); } while (0)
>>           |                              ^~~~~~~~~
>>     arch/alpha/include/asm/pgtable.h:293:9: note: in expansion of macro 'smp_rmb'
>>       293 |         smp_rmb(); /* see above */
>>           |         ^~~~~~~
> I had been wondering if barriers could be static __always_inline, like
> we do for atomic_t operations. Apparently this answers that questions.
>
> This should fix it:
> https://lkml.kernel.org/r/20211204125703.3344454-1-elver@google.com
>
> Unrelatedly, I wonder if I can get the test robot to also check some
> of my branches:

Hi Marco,

We have added it into our monitor list.

Best Regards,
Rong Chen

> https://git.kernel.org/pub/scm/linux/kernel/git/melver/linux.git/
> That'd be very useful, to catch things like this early, and avoid
> disturbing Paul too much. :-)
>
> Thanks,
> -- Marco


  reply	other threads:[~2021-12-07  0:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-04  5:32 kernel test robot
2021-12-04 13:02 ` Marco Elver
2021-12-07  0:32   ` Rong Chen [this message]
2021-12-07  6:11     ` [kbuild-all] " Marco Elver

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=78e4a2b0-af5c-d13c-ef33-878f84555b36@intel.com \
    --to=rong.a.chen@intel.com \
    --cc=elver@google.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=paulmck@kernel.org \
    /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®