From: syzbot <syzbot+ec9b5cce58002d184fb6@syzkaller.appspotmail.com>
To: davem@davemloft.net, dmantipov@yandex.ru, edumazet@google.com,
hdanton@sina.com, jhs@mojatatu.com, jiri@resnulli.us,
kuba@kernel.org, leandro.maciel.dorileo@intel.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, syzkaller-bugs@googlegroups.com,
vedang.patel@intel.com, vinicius.gomes@intel.com,
xiyou.wangcong@gmail.com
Subject: Re: [syzbot] [net?] WARNING: ODEBUG bug in advance_sched
Date: Mon, 11 Nov 2024 11:31:03 -0800 [thread overview]
Message-ID: <67325b77.050a0220.1fb99c.0151.GAE@google.com> (raw)
In-Reply-To: <000000000000f3d57d060d0556a1@google.com>
syzbot suspects this issue was fixed by commit:
commit f504465970aebb2467da548f7c1efbbf36d0f44b
Author: Dmitry Antipov <dmantipov@yandex.ru>
Date: Fri Oct 18 05:13:38 2024 +0000
net: sched: fix use-after-free in taprio_change()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13a7b4e8580000
start commit: fe46a7dd189e Merge tag 'sound-6.9-rc1' of git://git.kernel..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=fe78468a74fdc3b7
dashboard link: https://syzkaller.appspot.com/bug?extid=ec9b5cce58002d184fb6
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11b37db1180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1371c30d180000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: net: sched: fix use-after-free in taprio_change()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-11-11 19:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 13:47 [syzbot] [net?] WARNING: ODEBUG bug in advance_sched syzbot
2023-12-21 19:33 ` syzbot
2023-12-22 11:07 ` Hillf Danton
2023-12-22 11:37 ` syzbot
2024-11-11 19:31 ` syzbot [this message]
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=67325b77.050a0220.1fb99c.0151.GAE@google.com \
--to=syzbot+ec9b5cce58002d184fb6@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=dmantipov@yandex.ru \
--cc=edumazet@google.com \
--cc=hdanton@sina.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=leandro.maciel.dorileo@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vedang.patel@intel.com \
--cc=vinicius.gomes@intel.com \
--cc=xiyou.wangcong@gmail.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