From: syzbot <syzbot+55b82aea13452e3d128f@syzkaller.appspotmail.com>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
mingo@kernel.org, peterz@infradead.org,
reiserfs-devel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [reiserfs?] KASAN: use-after-free Read in leaf_paste_in_buffer
Date: Mon, 13 Mar 2023 15:42:19 -0700 [thread overview]
Message-ID: <000000000000d7988d05f6cfd256@google.com> (raw)
In-Reply-To: <000000000000e3af1a05eec2e287@google.com>
syzbot suspects this issue was fixed by commit:
commit 26388a7c353f7b1d3fd8a6df6452fa9773193155
Author: Peter Zijlstra <peterz@infradead.org>
Date: Thu Jan 12 19:44:03 2023 +0000
cpuidle,arch: Mark all regular cpuidle_state:: Enter methods __cpuidle
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16fc20aac80000
start commit: 420b2d431d18 Merge tag 'clk-fixes-for-linus' of git://git...
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=6bb1911ff9919df0
dashboard link: https://syzkaller.appspot.com/bug?extid=55b82aea13452e3d128f
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17249347480000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14281c1b480000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: cpuidle,arch: Mark all regular cpuidle_state:: Enter methods __cpuidle
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-03-13 22:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 11:54 [syzbot] KASAN: use-after-free Read in leaf_paste_in_buffer syzbot
2023-03-13 22:42 ` 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=000000000000d7988d05f6cfd256@google.com \
--to=syzbot+55b82aea13452e3d128f@syzkaller.appspotmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=reiserfs-devel@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.