From: syzbot <syzbot+401145a9a237779feb26@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com, clm@fb.com,
djwong@kernel.org, dsterba@suse.com, hch@infradead.org,
josef@toxicpanda.com, linux-btrfs@vger.kernel.org,
linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org,
ntfs3@lists.linux.dev, syzkaller-bugs@googlegroups.com,
torvalds@linux-foundation.org, willy@infradead.org
Subject: Re: [syzbot] [xfs?] BUG: unable to handle kernel paging request in clear_user_rep_good
Date: Sun, 30 Apr 2023 21:31:15 -0700 [thread overview]
Message-ID: <0000000000001ec6ce05fa9a4bf7@google.com> (raw)
In-Reply-To: <000000000000de34bd05f3c6fe19@google.com>
syzbot suspects this issue was fixed by commit:
commit d2c95f9d6802cc518d71d9795f4d9da54fb4e24d
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Sat Apr 15 20:22:31 2023 +0000
x86: don't use REP_GOOD or ERMS for user memory clearing
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13636ffc280000
start commit: ab072681eabe Merge tag 'irq_urgent_for_v6.2_rc6' of git://..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=23330449ad10b66f
dashboard link: https://syzkaller.appspot.com/bug?extid=401145a9a237779feb26
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13b3ba9e480000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: x86: don't use REP_GOOD or ERMS for user memory clearing
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-05-01 4:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 7:54 [syzbot] [ntfs3?] [btrfs?] BUG: unable to handle kernel paging request in clear_user_rep_good syzbot
2023-02-03 16:25 ` Christoph Hellwig
2023-02-03 16:32 ` Matthew Wilcox
2023-05-01 4:31 ` syzbot [this message]
2023-05-01 18:49 ` [syzbot] [xfs?] " Linus Torvalds
2023-05-03 10:31 ` Borislav Petkov
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=0000000000001ec6ce05fa9a4bf7@google.com \
--to=syzbot+401145a9a237779feb26@syzkaller.appspotmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=clm@fb.com \
--cc=djwong@kernel.org \
--cc=dsterba@suse.com \
--cc=hch@infradead.org \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.org \
--cc=willy@infradead.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 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).