Re: nft_pipapo_avx2_lookup backtrace in linux 5.10

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Arturo,

On Fri, 7 May 2021 11:26:51 +0200
Arturo Borrero Gonzalez <arturo@xxxxxxxxxxxxx> 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




[Index of Archives]     [Netfitler Users]     [Berkeley Packet Filter]     [LARTC]     [Bugtraq]     [Yosemite Forum]

  Powered by Linux