[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210513005608.GA23780@salvia>
Date: Thu, 13 May 2021 02:56:08 +0200
From: Pablo Neira Ayuso <pablo@...filter.org>
To: Florian Westphal <fw@...len.de>
Cc: Dmitry Vyukov <dvyukov@...gle.com>,
syzbot <syzbot+154bd5be532a63aa778b@...kaller.appspotmail.com>,
coreteam@...filter.org, David Miller <davem@...emloft.net>,
Jozsef Kadlecsik <kadlec@...filter.org>,
Jakub Kicinski <kuba@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
netdev <netdev@...r.kernel.org>,
NetFilter <netfilter-devel@...r.kernel.org>,
syzkaller-bugs <syzkaller-bugs@...glegroups.com>
Subject: Re: [syzbot] WARNING in __nf_unregister_net_hook (4)
On Sat, May 08, 2021 at 04:46:57PM +0200, Florian Westphal wrote:
> Dmitry Vyukov <dvyukov@...gle.com> wrote:
> > > IMPORTANT: if you fix the issue, please add the following tag to the commit:
> > > Reported-by: syzbot+154bd5be532a63aa778b@...kaller.appspotmail.com
> >
> > Is this also fixed by "netfilter: arptables: use pernet ops struct
> > during unregister"?
> > The warning is the same, but the stack is different...
>
> No, this is a different bug.
>
> In both cases the caller attempts to unregister a hook that the core
> can't find, but in this case the caller is nftables, not arptables.
I see no reproducer for this bug. Maybe I broke the dormant flag handling?
Or maybe syzbot got here after the arptables bug has been hitted?
Powered by blists - more mailing lists