From: Hillf Danton <hdanton@sina.com>
To: syzbot <syzbot+ebbab3e04c88fa141e6b@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [netfilter?] WARNING: ODEBUG bug in ip_set_free
Date: Wed, 14 Feb 2024 08:55:51 +0800 [thread overview]
Message-ID: <20240214005553.1060-1-hdanton@sina.com> (raw)
In-Reply-To: <000000000000d42dae0611477922@google.com>
On Tue, 13 Feb 2024 10:22:24 -0800
> HEAD commit: f735966ee23c Merge branches 'for-next/reorg-va-space' and ..
> git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=161a6ba2180000
#syz test https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
--- x/net/netfilter/ipset/ip_set_bitmap_gen.h
+++ y/net/netfilter/ipset/ip_set_bitmap_gen.h
@@ -60,6 +60,7 @@ mtype_destroy(struct ip_set *set)
{
struct mtype *map = set->data;
+ del_timer_sync(&map->gc);
if (set->dsize && set->extensions & IPSET_EXT_DESTROY)
mtype_ext_cleanup(set);
ip_set_free(map->members);
--
next prev parent reply other threads:[~2024-02-14 0:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 18:22 syzbot
2024-02-14 0:55 ` Hillf Danton [this message]
2024-02-14 3:44 ` syzbot
2024-02-14 8:58 ` Jozsef Kadlecsik
2024-02-14 9:15 ` [syzbot] #syz test: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci syzbot
2024-02-14 9:18 ` syzbot
2024-02-15 11:38 ` [syzbot] Re: WARNING: ODEBUG bug in ip_set_free syzbot
2024-02-15 12:39 ` [syzbot] Re: [syzbot] [netfilter?] " syzbot
[not found] <71fab85e-966d-ba46-faec-a75a283bd325@netfilter.org>
2024-02-14 9:35 ` syzbot
[not found] <9cf86b72-286d-f726-6907-ff2c11af6d75@blackhole.kfki.hu>
2024-02-14 9:52 ` syzbot
[not found] <20240215113851.GE25716@breakpoint.cc>
2024-02-15 12:25 ` 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=20240214005553.1060-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+ebbab3e04c88fa141e6b@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
all inboxes | Powered by JetHome®