From: syzbot <syzbot+644848628d5e12d5438c@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, gregkh@linuxfoundation.org,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, lrh2000@pku.edu.cn, seanjc@google.com,
stern@rowland.harvard.edu, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [kernel?] kernel BUG in workingset_activation (2)
Date: Wed, 28 Jun 2023 01:00:45 -0700 [thread overview]
Message-ID: <0000000000001e68bd05ff2bfbbf@google.com> (raw)
In-Reply-To: <000000000000a2c79f05ed84c7f9@google.com>
syzbot suspects this issue was fixed by commit:
commit 0143d148d1e882fb1538dc9974c94d63961719b9
Author: Ruihan Li <lrh2000@pku.edu.cn>
Date: Mon May 15 13:09:55 2023 +0000
usb: usbfs: Enforce page requirements for mmap
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10a65abd280000
start commit: 59d0d52c30d4 AMerge tag 'netfs-fixes-20221115' of git://gi..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=11d3fa0b3feb5055
dashboard link: https://syzkaller.appspot.com/bug?extid=644848628d5e12d5438c
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14fdf3f1880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17b54702880000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: usb: usbfs: Enforce page requirements for mmap
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-06-28 8:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 16:23 [syzbot] kernel BUG in workingset_activation (2) syzbot
2022-11-15 19:27 ` Andrew Morton
2022-11-15 20:07 ` Sean Christopherson
2023-06-28 8:00 ` syzbot [this message]
2023-06-28 8:20 ` [syzbot] [kernel?] " Ruihan Li
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=0000000000001e68bd05ff2bfbbf@google.com \
--to=syzbot+644848628d5e12d5438c@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lrh2000@pku.edu.cn \
--cc=seanjc@google.com \
--cc=stern@rowland.harvard.edu \
--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