From: Stefano Brivio <sbrivio@redhat.com>
To: kernel test robot <lkp@intel.com>
Cc: Florian Westphal <fw@strlen.de>,
Pablo Neira Ayuso <pablo@netfilter.org>,
LKML <linux-kernel@vger.kernel.org>,
lkp@lists.01.org
Subject: Re: [netfilter] e32a4dc651: BUG:using_smp_processor_id()in_preemptible
Date: Fri, 5 Jun 2020 00:23:23 +0200 [thread overview]
Message-ID: <20200605002323.501b1cc6@redhat.com> (raw)
In-Reply-To: <20200603084934.GF12456@shao2-debian>
Hi,
On Wed, 3 Jun 2020 16:49:34 +0800
kernel test robot <lkp@intel.com> wrote:
> Greeting,
>
> FYI, we noticed the following commit (built with gcc-7):
>
> commit: e32a4dc6512ce3c1a1920531246e7037896e510a ("netfilter: nf_tables: make sets built-in")
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
>
> in testcase: kernel-selftests
> with following parameters:
>
> group: kselftests-netfilter
I couldn't find this information in the report. Would it be possible to
have here an indication of what kselftest specifically is failing?
There are a number of tests in that group. I have an obvious suspicion
here (nft_concat_range.sh), but it would be nice to know, in general.
> [...]
>
> [ 165.316525] BUG: using smp_processor_id() in preemptible [00000000] code: nft/6247
> [ 165.319547] caller is nft_pipapo_insert+0x464/0x610 [nf_tables]
I'll take care of this, thanks Florian for forwarding.
--
Stefano
next prev parent reply other threads:[~2020-06-04 22:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 8:49 [netfilter] e32a4dc651: BUG:using_smp_processor_id()in_preemptible kernel test robot
2020-06-04 22:23 ` Stefano Brivio [this message]
2020-06-05 0:15 ` [LKP] " Liu Yiding
2020-06-05 0:25 ` Stefano Brivio
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=20200605002323.501b1cc6@redhat.com \
--to=sbrivio@redhat.com \
--cc=fw@strlen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=pablo@netfilter.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;
as well as URLs for NNTP newsgroup(s).