From: Marco Elver <elver@google.com>
To: kbuild-all@lists.01.org
Subject: Re: [linux-next:master 4752/5235] kernel/kcsan/kcsan_test.c:592:35: error: implicit declaration of function 'clear_bit_unlock_is_negative_byte'
Date: Mon, 06 Dec 2021 18:43:35 +0100 [thread overview]
Message-ID: <CANpmjNPy0ySAp3YV7Bo==-gp-RnRTripZFrL2fNRkBvxRURhPg@mail.gmail.com> (raw)
In-Reply-To: <202112070117.78ld7W01-lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1568 bytes --]
On Mon, 6 Dec 2021 at 18:40, kernel test robot <lkp@intel.com> wrote:
[...]
> kernel/kcsan/kcsan_test.c: In function 'test_barrier_nothreads':
> >> kernel/kcsan/kcsan_test.c:592:35: error: implicit declaration of function 'clear_bit_unlock_is_negative_byte' [-Werror=implicit-function-declaration]
> 592 | KCSAN_EXPECT_READ_BARRIER(clear_bit_unlock_is_negative_byte(0, &test_var), true);
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> kernel/kcsan/kcsan_test.c:537:17: note: in definition of macro '__KCSAN_EXPECT_BARRIER'
> 537 | barrier; \
> | ^~~~~~~
> kernel/kcsan/kcsan_test.c:592:9: note: in expansion of macro 'KCSAN_EXPECT_READ_BARRIER'
> 592 | KCSAN_EXPECT_READ_BARRIER(clear_bit_unlock_is_negative_byte(0, &test_var), true);
> | ^~~~~~~~~~~~~~~~~~~~~~~~~
> kernel/kcsan/kcsan_test.c: In function 'test_atomic_builtins':
> kernel/kcsan/kcsan_test.c:1233:17: warning: 'atomic_thread_fence' is not supported with '-fsanitize=thread' [-Wtsan]
> 1233 | __atomic_thread_fence(__ATOMIC_SEQ_CST);
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> cc1: some warnings being treated as errors
FTR, like the other issue, fixed by same patch:
https://lore.kernel.org/all/20211206064151.3337384-2-elver(a)google.com/
But I'm glad to see the test robot discovered this, too.
Thanks,
-- Marco
WARNING: multiple messages have this Message-ID (diff)
From: Marco Elver <elver@google.com>
To: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
"Paul E. McKenney" <paulmck@kernel.org>
Subject: Re: [linux-next:master 4752/5235] kernel/kcsan/kcsan_test.c:592:35: error: implicit declaration of function 'clear_bit_unlock_is_negative_byte'
Date: Mon, 6 Dec 2021 18:43:35 +0100 [thread overview]
Message-ID: <CANpmjNPy0ySAp3YV7Bo==-gp-RnRTripZFrL2fNRkBvxRURhPg@mail.gmail.com> (raw)
In-Reply-To: <202112070117.78ld7W01-lkp@intel.com>
On Mon, 6 Dec 2021 at 18:40, kernel test robot <lkp@intel.com> wrote:
[...]
> kernel/kcsan/kcsan_test.c: In function 'test_barrier_nothreads':
> >> kernel/kcsan/kcsan_test.c:592:35: error: implicit declaration of function 'clear_bit_unlock_is_negative_byte' [-Werror=implicit-function-declaration]
> 592 | KCSAN_EXPECT_READ_BARRIER(clear_bit_unlock_is_negative_byte(0, &test_var), true);
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> kernel/kcsan/kcsan_test.c:537:17: note: in definition of macro '__KCSAN_EXPECT_BARRIER'
> 537 | barrier; \
> | ^~~~~~~
> kernel/kcsan/kcsan_test.c:592:9: note: in expansion of macro 'KCSAN_EXPECT_READ_BARRIER'
> 592 | KCSAN_EXPECT_READ_BARRIER(clear_bit_unlock_is_negative_byte(0, &test_var), true);
> | ^~~~~~~~~~~~~~~~~~~~~~~~~
> kernel/kcsan/kcsan_test.c: In function 'test_atomic_builtins':
> kernel/kcsan/kcsan_test.c:1233:17: warning: 'atomic_thread_fence' is not supported with '-fsanitize=thread' [-Wtsan]
> 1233 | __atomic_thread_fence(__ATOMIC_SEQ_CST);
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> cc1: some warnings being treated as errors
FTR, like the other issue, fixed by same patch:
https://lore.kernel.org/all/20211206064151.3337384-2-elver@google.com/
But I'm glad to see the test robot discovered this, too.
Thanks,
-- Marco
next prev parent reply other threads:[~2021-12-06 17:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 17:40 [linux-next:master 4752/5235] kernel/kcsan/kcsan_test.c:592:35: error: implicit declaration of function 'clear_bit_unlock_is_negative_byte' kernel test robot
2021-12-06 17:40 ` kernel test robot
2021-12-06 17:43 ` Marco Elver [this message]
2021-12-06 17:43 ` 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='CANpmjNPy0ySAp3YV7Bo==-gp-RnRTripZFrL2fNRkBvxRURhPg@mail.gmail.com' \
--to=elver@google.com \
--cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.