From: syzbot <syzbot+b65e0af58423fc8a73aa@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] KASAN: slab-use-after-free Read in advance_sched
Date: Fri, 23 Feb 2024 16:15:05 -0800 [thread overview]
Message-ID: <0000000000008c49c3061215913e@google.com> (raw)
In-Reply-To: <20240223230204.297-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+b65e0af58423fc8a73aa@syzkaller.appspotmail.com
Tested on:
commit: 9abbc241 Merge branch 'for-next/core' into for-kernelci
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=12633cc4180000
kernel config: https://syzkaller.appspot.com/x/.config?x=af5c6c699e57bbb3
dashboard link: https://syzkaller.appspot.com/bug?extid=b65e0af58423fc8a73aa
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
patch: https://syzkaller.appspot.com/x/patch.diff?x=138fea02180000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2024-02-24 0:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 0:19 [syzbot] [net?] KASAN: slab-use-after-free Read in advance_sched syzbot
2024-02-23 9:29 ` syzbot
2024-02-23 23:02 ` Hillf Danton
2024-02-24 0:15 ` syzbot [this message]
2024-09-30 11:14 ` [syzbot] " syzbot
2024-09-30 11:48 ` syzbot
-- strict thread matches above, loose matches on Subject: below --
2023-12-25 0:55 xingwei lee
2023-12-25 23:06 ` Jamal Hadi Salim
2023-12-26 0:55 ` xingwei lee
2023-12-26 1:12 ` Jamal Hadi Salim
[not found] <20240930111450.649145-1-dmantipov@yandex.ru>
2024-09-30 15:08 ` syzbot
[not found] <20240930114812.653517-1-dmantipov@yandex.ru>
2024-09-30 15:22 ` 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=0000000000008c49c3061215913e@google.com \
--to=syzbot+b65e0af58423fc8a73aa@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 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.