From: syzbot <syzbot+4fd66a69358fc15ae2ad@syzkaller.appspotmail.com>
To: fw@strlen.de, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [netfilter?] KASAN: slab-use-after-free Read in nf_tables_trans_destroy_work
Date: Tue, 02 Jul 2024 06:33:04 -0700 [thread overview]
Message-ID: <000000000000ddef5a061c43c0c0@google.com> (raw)
In-Reply-To: <20240702093924.GA23593@breakpoint.cc>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+4fd66a69358fc15ae2ad@syzkaller.appspotmail.com
Tested on:
commit: f2a491c9 netfilter: nf_tables: unconditionally flush p..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/fwestphal/nf-next.git flush_uncond
console output: https://syzkaller.appspot.com/x/log.txt?x=1626b9c6980000
kernel config: https://syzkaller.appspot.com/x/.config?x=e78fc116033e0ab7
dashboard link: https://syzkaller.appspot.com/bug?extid=4fd66a69358fc15ae2ad
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2024-07-02 13:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240702093924.GA23593@breakpoint.cc>
2024-07-02 13:33 ` syzbot [this message]
2024-07-05 10:48 [PATCH nf] netfilter: nf_tables: unconditionally flush pending work before notifier Hillf Danton
2024-07-05 11:18 ` [syzbot] [netfilter?] KASAN: slab-use-after-free Read in nf_tables_trans_destroy_work syzbot
-- strict thread matches above, loose matches on Subject: below --
2024-07-01 20:19 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: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=000000000000ddef5a061c43c0c0@google.com \
--to=syzbot+4fd66a69358fc15ae2ad@syzkaller.appspotmail.com \
--cc=fw@strlen.de \
--cc=linux-kernel@vger.kernel.org \
--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 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.