From: syzbot <syzbot+b7ad168b779385f8cd58@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, hdanton@sina.com, jack@suse.cz,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, liushixin2@huawei.com,
syzkaller-bugs@googlegroups.com, tujinjiang@huawei.com,
willy@infradead.org
Subject: Re: [syzbot] [mm?] INFO: task hung in __unmap_and_move (4)
Date: Sun, 09 Jun 2024 23:41:03 -0700 [thread overview]
Message-ID: <000000000000e034e7061a836eb4@google.com> (raw)
In-Reply-To: <000000000000e5738d05f0f46309@google.com>
syzbot suspects this issue was fixed by commit:
commit 0fd44ab213bcfb26c47eedaa0985e4b5dbf0a494
Author: Liu Shixin <liushixin2@huawei.com>
Date: Fri Mar 22 09:35:54 2024 +0000
mm/readahead: break read-ahead loop if filemap_add_folio return -ENOMEM
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10fabe96980000
start commit: 72a85e2b0a1e Merge tag 'spi-fix-v6.2-rc1' of git://git.ker..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=4db06888b17328d6
dashboard link: https://syzkaller.appspot.com/bug?extid=b7ad168b779385f8cd58
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=143d0688480000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=154e3cac480000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: mm/readahead: break read-ahead loop if filemap_add_folio return -ENOMEM
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-06-10 6:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-29 9:48 [syzbot] INFO: task hung in __unmap_and_move (4) syzbot
2022-12-29 22:01 ` Matthew Wilcox
2024-06-10 6:41 ` 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=000000000000e034e7061a836eb4@google.com \
--to=syzbot+b7ad168b779385f8cd58@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=hdanton@sina.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liushixin2@huawei.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tujinjiang@huawei.com \
--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