From: syzbot <syzbot+756fe9affda890e892ae@syzkaller.appspotmail.com>
To: acme@kernel.org, adrian.hunter@intel.com,
alexander.shishkin@linux.intel.com, bpf@vger.kernel.org,
irogers@google.com, jolsa@kernel.org,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
mark.rutland@arm.com, mingo@kernel.org, mingo@redhat.com,
namhyung@kernel.org, netdev@vger.kernel.org,
peterz@infradead.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [perf?] general protection fault in inherit_task_group
Date: Wed, 29 Nov 2023 04:17:05 -0800 [thread overview]
Message-ID: <0000000000006547d3060b498385@google.com> (raw)
In-Reply-To: <000000000000d9483d060901f460@google.com>
syzbot suspects this issue was fixed by commit:
commit a71ef31485bb51b846e8db8b3a35e432cc15afb5
Author: Peter Zijlstra <peterz@infradead.org>
Date: Tue Oct 24 09:42:21 2023 +0000
perf/core: Fix potential NULL deref
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17172162e80000
start commit: 6808918343a8 net: bridge: fill in MODULE_DESCRIPTION()
git tree: bpf-next
kernel config: https://syzkaller.appspot.com/x/.config?x=429fa76d04cf393c
dashboard link: https://syzkaller.appspot.com/bug?extid=756fe9affda890e892ae
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12db572b680000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10839a1b680000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: perf/core: Fix potential NULL deref
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-11-29 12:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 12:04 [syzbot] [perf?] general protection fault in inherit_task_group syzbot
2023-10-31 12:16 ` Peter Zijlstra
2023-11-29 12:17 ` syzbot [this message]
2023-11-29 12:21 ` Aleksandr Nogikh
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=0000000000006547d3060b498385@google.com \
--to=syzbot+756fe9affda890e892ae@syzkaller.appspotmail.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bpf@vger.kernel.org \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).