From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Matthias Maier <tamiko@43-1.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
netfilter-devel@vger.kernel.org
Subject: Re: Kernel oops with netfilter: nf_tables: incorrect error path handling with NFT_MSG_NEWRULE
Date: Mon, 26 Jun 2023 01:05:41 +0200 [thread overview]
Message-ID: <ZJjIRQevLKW+YJP6@calendula> (raw)
In-Reply-To: <87cz1j5tof.fsf@43-1.org>
Hi,
On Sun, Jun 25, 2023 at 12:38:08PM -0500, Matthias Maier wrote:
> Dear all,
>
> commit 1240eb93f0616b21c675416516ff3d74798fdc97
> aka bdace3b1a51887211d3e49417a18fdbd315a313b (linux-6.3.y)
> netfilter: nf_tables: incorrect error path handling with NFT_MSG_NEWRULE
>
> causes a kernel oops on my side when booting my machine; see attached.
>
> Reverting this commit fixes the kernel oops.
> Tested on 6.3.9 and 6.4.0-rc7
Could you give a try to these two fixes on top?
26b5a5712eb8 netfilter: nf_tables: add NFT_TRANS_PREPARE_ERROR to deal with bound set/chain
4bedf9eee016 netfilter: nf_tables: fix chain binding transaction logic
These patches are scheduled for 6.4
You might also need this one on top:
https://patchwork.ozlabs.org/project/netfilter-devel/patch/20230625224219.64876-1-pablo@netfilter.org/
If problem still persists, a reproducer would be good to have.
Thanks.
next prev parent reply other threads:[~2023-06-25 23:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-25 17:38 Kernel oops with netfilter: nf_tables: incorrect error path handling with NFT_MSG_NEWRULE Matthias Maier
2023-06-25 23:05 ` Pablo Neira Ayuso [this message]
2023-06-26 5:22 ` Matthias Maier
2023-06-26 8:12 ` Linux regression tracking #adding (Thorsten Leemhuis)
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=ZJjIRQevLKW+YJP6@calendula \
--to=pablo@netfilter.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tamiko@43-1.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.