From: syzbot <syzbot+2e3efb5eb71cb5075ba7@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] WARNING: ODEBUG bug in route4_destroy
Date: Thu, 16 Jun 2022 09:16:07 -0700 [thread overview]
Message-ID: <00000000000088f98505e192f46e@google.com> (raw)
In-Reply-To: <20220616132136.2669-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+2e3efb5eb71cb5075ba7@syzkaller.appspotmail.com
Tested on:
commit: 018ab4fa netfs: fix up netfs_inode_init() docbook comm..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=10c31fbff00000
kernel config: https://syzkaller.appspot.com/x/.config?x=f21890d74080ef72
dashboard link: https://syzkaller.appspot.com/bug?extid=2e3efb5eb71cb5075ba7
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=1627e7a0080000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2022-06-16 16:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220616132136.2669-1-hdanton@sina.com>
2022-06-16 16:16 ` syzbot [this message]
[not found] <20220616123726.2597-1-hdanton@sina.com>
2022-06-16 12:56 ` [syzbot] WARNING: ODEBUG bug in route4_destroy syzbot
[not found] <20220616121345.2536-1-hdanton@sina.com>
2022-06-16 12:26 ` syzbot
[not found] <20220616112635.2462-1-hdanton@sina.com>
2022-06-16 11:42 ` syzbot
[not found] <20220616104752.2392-1-hdanton@sina.com>
2022-06-16 10:59 ` syzbot
[not found] <20220615140453.2269-1-hdanton@sina.com>
2022-06-15 14:27 ` syzbot
[not found] <20220615121701.2143-1-hdanton@sina.com>
2022-06-15 12:32 ` syzbot
[not found] <20220615104440.1997-1-hdanton@sina.com>
2022-06-15 10:55 ` syzbot
2021-09-04 16:46 syzbot
2022-06-14 14:35 ` Zhen Chen
2022-06-14 14:46 ` Dan Carpenter
2022-06-15 11:57 ` Zhen Chen
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=00000000000088f98505e192f46e@google.com \
--to=syzbot+2e3efb5eb71cb5075ba7@syzkaller.appspotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox