From: syzbot <syzbot+03cfa0c5a0bcba3bf195@syzkaller.appspotmail.com>
To: ardb@kernel.org, bp@alien8.de, dave.hansen@linux.intel.com,
djwong@kernel.org, hpa@zytor.com, jbaron@akamai.com,
jpoimboe@kernel.org, linux-kernel@vger.kernel.org,
mingo@redhat.com, peterz@infradead.org, rostedt@goodmis.org,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
x86@kernel.org
Subject: Re: [syzbot] [kernel?] kernel BUG in __jump_label_patch
Date: Fri, 20 Sep 2024 23:01:02 -0700 [thread overview]
Message-ID: <66ee611e.050a0220.3195df.0035.GAE@google.com> (raw)
In-Reply-To: <00000000000070a181061bc8b256@google.com>
syzbot suspects this issue was fixed by commit:
commit 224fa3552029a3d14bec7acf72ded8171d551b88
Author: Peter Zijlstra <peterz@infradead.org>
Date: Wed Jul 31 10:43:21 2024 +0000
jump_label: Fix the fix, brown paper bags galore
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1719ff00580000
start commit: 2c9b3512402e Merge tag 'for-linus' of git://git.kernel.org..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=f463ee48656fea03
dashboard link: https://syzkaller.appspot.com/bug?extid=03cfa0c5a0bcba3bf195
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=128eca3d980000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: jump_label: Fix the fix, brown paper bags galore
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-09-21 6:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 10:44 [syzbot] [kernel?] kernel BUG in __jump_label_patch syzbot
2024-09-21 6:01 ` 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=66ee611e.050a0220.3195df.0035.GAE@google.com \
--to=syzbot+03cfa0c5a0bcba3bf195@syzkaller.appspotmail.com \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=djwong@kernel.org \
--cc=hpa@zytor.com \
--cc=jbaron@akamai.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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.