From: syzbot <syzbot+95f1db35defd8524f1dd@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, ansuelsmth@gmail.com, axboe@kernel.dk,
david@redhat.com, dianders@google.com,
kirill.shutemov@linux.intel.com, lilingfeng3@huawei.com,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
riyandhiman14@gmail.com, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [block?] BUG: sleeping function called from invalid context in unmap_mapping_folio
Date: Tue, 04 Feb 2025 21:58:03 -0800 [thread overview]
Message-ID: <67a2fdeb.050a0220.50516.000e.GAE@google.com> (raw)
In-Reply-To: <67a23341.050a0220.163cdc.0069.GAE@google.com>
syzbot has bisected this issue to:
commit 1760a1b5aacbe00dec464b1bf2b10443c10377ad
Author: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
Date: Thu Jan 30 10:00:45 2025 +0000
mm/vmscan: use PG_dropbehind instead of PG_reclaim in shrink_folio_list()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14c2ef64580000
start commit: 40b8e93e17bf Add linux-next specific files for 20250204
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=16c2ef64580000
console output: https://syzkaller.appspot.com/x/log.txt?x=12c2ef64580000
kernel config: https://syzkaller.appspot.com/x/.config?x=ec880188a87c6aad
dashboard link: https://syzkaller.appspot.com/bug?extid=95f1db35defd8524f1dd
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16010df8580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12f078a4580000
Reported-by: syzbot+95f1db35defd8524f1dd@syzkaller.appspotmail.com
Fixes: 1760a1b5aacb ("mm/vmscan: use PG_dropbehind instead of PG_reclaim in shrink_folio_list()")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-02-05 5:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 15:33 [syzbot] [block?] BUG: sleeping function called from invalid context in unmap_mapping_folio syzbot
2025-02-05 5:58 ` 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=67a2fdeb.050a0220.50516.000e.GAE@google.com \
--to=syzbot+95f1db35defd8524f1dd@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=ansuelsmth@gmail.com \
--cc=axboe@kernel.dk \
--cc=david@redhat.com \
--cc=dianders@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=lilingfeng3@huawei.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riyandhiman14@gmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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