From: Stefano Brivio <sbrivio@redhat.com>
To: Arturo Borrero Gonzalez <arturo@netfilter.org>
Cc: "netfilter-devel@vger.kernel.org" <netfilter-devel@vger.kernel.org>
Subject: Re: nft_pipapo_avx2_lookup backtrace in linux 5.10
Date: Fri, 7 May 2021 12:36:36 +0200 [thread overview]
Message-ID: <20210507123636.030e98ef@elisabeth> (raw)
In-Reply-To: <8ff71ad7-7171-c8c7-f31b-d4bd7577cc18@netfilter.org>
Hi Arturo,
On Fri, 7 May 2021 11:26:51 +0200
Arturo Borrero Gonzalez <arturo@netfilter.org> wrote:
> Hi there,
>
> I got this backtrace in one of my servers. I wonder if it is known or fixed
> already in a later version.
Not as far as I know. At a glance:
> [...]
>
> [Thu May 6 16:20:21 2021] nft_pipapo_avx2_lookup+0x4c/0x1cba [nf_tables]
>
> [...]
>
> [Thu May 6 16:20:21 2021] asm_common_interrupt+0x1e/0x40
> [Thu May 6 16:20:21 2021] RIP: 0010:crc_41+0x0/0x1e [crc32c_intel]
we probably need to add an irq_fpu_usable() check in
nft_pipapo_avx2_lookup() and fall back to nft_pipapo_avx2_lookup_slow()
if that returns false, but I haven't looked into this thoroughly yet.
Can you reproduce this reliably? That would be helpful.
--
Stefano
next prev parent reply other threads:[~2021-05-07 10:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-07 9:26 nft_pipapo_avx2_lookup backtrace in linux 5.10 Arturo Borrero Gonzalez
2021-05-07 10:35 ` Florian Westphal
2021-05-07 10:52 ` Stefano Brivio
2021-05-08 1:00 ` Stefano Brivio
2021-05-09 11:00 ` Arturo Borrero Gonzalez
2021-05-07 10:36 ` Stefano Brivio [this message]
2021-05-07 11:12 ` Arturo Borrero Gonzalez
2021-05-08 1:00 ` Stefano Brivio
2021-05-09 10:58 ` Arturo Borrero Gonzalez
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=20210507123636.030e98ef@elisabeth \
--to=sbrivio@redhat.com \
--cc=arturo@netfilter.org \
--cc=netfilter-devel@vger.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 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.