<html>
<head>
<base href="https://bugzilla.netfilter.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - RIP: 0010:nft_set_elem_expr_destroy+0x30/0xb0 [nf_tables]"
href="https://bugzilla.netfilter.org/show_bug.cgi?id=1727#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - RIP: 0010:nft_set_elem_expr_destroy+0x30/0xb0 [nf_tables]"
href="https://bugzilla.netfilter.org/show_bug.cgi?id=1727">bug 1727</a>
from <span class="vcard"><a class="email" href="mailto:pablo@netfilter.org" title="Pablo Neira Ayuso <pablo@netfilter.org>"> <span class="fn">Pablo Neira Ayuso</span></a>
</span></b>
<pre>(In reply to xerro from <a href="show_bug.cgi?id=1727#c0">comment #0</a>)
<span class="quote">> Created <span class=""><a href="attachment.cgi?id=733" name="attach_733" title="dmesg stacktrace">attachment 733</a> <a href="attachment.cgi?id=733&action=edit" title="dmesg stacktrace">[details]</a></span>
> dmesg stacktrace
>
> Hello,
> This is my first bug report, I hope I am posting this issue in the correct
> place.
>
> I have a userland application which updates dynamically the nft set
> elements. I noticed that the filtering (nft) configuration was not changing.
>
> I tried to check the applied rules and set elements using the 'nft list
> ruleset' command, but the command hung up and never end.
>
> I noticed through the dmesg command that some kind of kernel error did
> happend. I copied the log locally (check attached logfile) and tried to
> reboot the VM. The VM never finished rebooting and I had to do a hard reset
> on the VM.</span >
Yes, this is a crash.
<span class="quote">> Some info if it helps troubleshooting the issue:
>
> # uname -a
> Linux HOU4716977 6.2.0-37-generic #38-Ubuntu SMP PREEMPT_DYNAMIC Mon Oct 30
> 21:04:52 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux</span >
There is a good number of fixes that have been backported up to -stable kernels
since summer 2023, but there is no -stable 6.2 kernel, you might have to
contact Ubuntu.
Unless you have a reproducer, this might be an old bug.
I believe Ubuntu 22.04 (which I think it is was you are using) that offers 5.15
which might provide -stable kernels.
Another possibility is to compile your own kernel based on -stable 6.1 to
confirm this problem is not there.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are watching all bug changes.</li>
</ul>
</body>
</html>