From: syzbot <syzbot+3538a6a72efa8b059c38@syzkaller.appspotmail.com>
To: dhowells@redhat.com, hdanton@sina.com,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] KASAN: use-after-free Read in rxrpc_lookup_local
Date: Tue, 06 Dec 2022 19:42:20 -0800 [thread overview]
Message-ID: <00000000000033009b05ef34b511@google.com> (raw)
In-Reply-To: <20221207030740.7663-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+3538a6a72efa8b059c38@syzkaller.appspotmail.com
Tested on:
commit: c9f8d736 net: mtk_eth_soc: enable flow offload support..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git
console output: https://syzkaller.appspot.com/x/log.txt?x=1205f597880000
kernel config: https://syzkaller.appspot.com/x/.config?x=c608c21151db14f2
dashboard link: https://syzkaller.appspot.com/bug?extid=3538a6a72efa8b059c38
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
patch: https://syzkaller.appspot.com/x/patch.diff?x=13c7a51d880000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2022-12-07 3:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221207030740.7663-1-hdanton@sina.com>
2022-12-07 3:42 ` syzbot [this message]
2022-12-07 11:57 ` [syzbot] KASAN: use-after-free Read in rxrpc_lookup_local David Howells
[not found] ` <20221207134234.7879-1-hdanton@sina.com>
2022-12-07 16:30 ` David Howells
2022-12-06 16:34 syzbot
2022-12-06 21:09 ` David Howells
2022-12-07 3:09 ` syzbot
2022-12-07 17:43 ` David Howells
2022-12-07 23:16 ` syzbot
[not found] ` <20221208035617.8037-1-hdanton@sina.com>
2022-12-08 8:53 ` David Howells
2022-12-08 11:20 ` David Howells
2022-12-08 12:02 ` 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=00000000000033009b05ef34b511@google.com \
--to=syzbot+3538a6a72efa8b059c38@syzkaller.appspotmail.com \
--cc=dhowells@redhat.com \
--cc=hdanton@sina.com \
--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.