From: Hillf Danton <hdanton@sina.com>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
syzbot+4fd66a69358fc15ae2ad@syzkaller.appspotmail.com
Subject: Re: [PATCH nf] netfilter: nf_tables: unconditionally flush pending work before notifier
Date: Sun, 7 Jul 2024 15:56:44 +0800 [thread overview]
Message-ID: <20240707075644.752-1-hdanton@sina.com> (raw)
In-Reply-To: <20240705110218.GA1616@breakpoint.cc>
On Fri, 5 Jul 2024 13:02:18 +0200 Florian Westphal <fw@strlen.de>
> Hillf Danton <hdanton@sina.com> wrote:
> > > lock trans mutex returns
> > > flush work
> > > free A
> > > unlock trans mutex
> > >
> > If your patch is correct, it should survive a warning.
> >
> > #syz test https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git 1c5fc27bc48a
> >
> > --- x/net/netfilter/nf_tables_api.c
> > +++ y/net/netfilter/nf_tables_api.c
> > @@ -11552,9 +11552,10 @@ static int nft_rcv_nl_event(struct notif
> >
> > gc_seq = nft_gc_seq_begin(nft_net);
> >
> > - if (!list_empty(&nf_tables_destroy_list))
> > - nf_tables_trans_destroy_flush_work();
> > + nf_tables_trans_destroy_flush_work();
> > again:
> > + WARN_ON(!list_empty(&nft_net->commit_list));
> > +
>
> You could officially submit this patch to nf-next, this
> is a slow path and the transaction list must be empty here.
>
> I think this change might be useful as it also documents
> this requirement.
Yes it is boy and the current reproducer triggered another warning [1,2].
[1] https://lore.kernel.org/lkml/20240706231332.3261-1-hdanton@sina.com/
[2] https://lore.kernel.org/lkml/000000000000a42289061c9d452e@google.com/
And feel free to take a look at fput() and sock_put() for instance of
freeing slab pieces asyncally.
next prev parent reply other threads:[~2024-07-07 7:57 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 20:19 [syzbot] [netfilter?] KASAN: slab-use-after-free Read in nf_tables_trans_destroy_work syzbot
2024-07-02 9:39 ` [syzbot] " syzbot
2024-07-02 11:28 ` Hillf Danton
2024-07-02 13:57 ` syzbot
2024-07-02 13:14 ` Edward Adam Davis
2024-07-02 14:13 ` syzbot
2024-07-02 14:08 ` [PATCH nf] netfilter: nf_tables: unconditionally flush pending work before notifier Florian Westphal
2024-07-03 10:35 ` Hillf Danton
2024-07-03 10:52 ` Florian Westphal
2024-07-03 12:09 ` Hillf Danton
2024-07-03 13:01 ` Florian Westphal
2024-07-04 10:35 ` Hillf Danton
2024-07-04 10:54 ` Florian Westphal
2024-07-05 10:48 ` Hillf Danton
2024-07-05 11:02 ` Florian Westphal
2024-07-07 7:56 ` Hillf Danton [this message]
2024-07-07 8:08 ` Florian Westphal
2024-07-08 10:56 ` Hillf Danton
2024-07-08 11:58 ` Florian Westphal
2024-07-08 12:17 ` Hillf Danton
2024-07-08 12:43 ` Florian Westphal
2024-07-05 11:18 ` [syzbot] [netfilter?] KASAN: slab-use-after-free Read in nf_tables_trans_destroy_work syzbot
2024-07-02 14:55 ` Edward Adam Davis
2024-07-02 15:28 ` syzbot
2024-07-06 23:13 ` Hillf Danton
2024-07-07 0:21 ` syzbot
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=20240707075644.752-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=fw@strlen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=syzbot+4fd66a69358fc15ae2ad@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/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