From: syzbot <syzbot+7bb5e48f6ead66c72906@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, david@redhat.com, dvyukov@google.com,
elver@google.com, glider@google.com, kasan-dev@googlegroups.com,
keescook@chromium.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, mcgrof@kernel.org, mhiramat@kernel.org,
mhocko@suse.com, mike.kravetz@oracle.com, muchun.song@linux.dev,
osalvador@suse.de, syzkaller-bugs@googlegroups.com,
torvalds@linux-foundation.org, vbabka@suse.cz
Subject: Re: [syzbot] [mm?] INFO: task hung in hugetlb_fault
Date: Wed, 03 Sep 2025 20:36:03 -0700 [thread overview]
Message-ID: <68b90923.050a0220.3db4df.020e.GAE@google.com> (raw)
In-Reply-To: <000000000000939d0a0621818f1e@google.com>
syzbot suspects this issue was fixed by commit:
commit 2ae1ab9934c785b855583e3eabd208d6f3ac91e1
Author: Oscar Salvador <osalvador@suse.de>
Date: Mon Jun 30 14:42:08 2025 +0000
mm,hugetlb: change mechanism to detect a COW on private mapping
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1289ea42580000
start commit: 87d6aab2389e Merge tag 'for_linus' of git://git.kernel.org..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=fb6ea01107fa96bd
dashboard link: https://syzkaller.appspot.com/bug?extid=7bb5e48f6ead66c72906
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17dd6327980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16d24f9f980000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: mm,hugetlb: change mechanism to detect a COW on private mapping
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-09-04 3:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-07 6:23 syzbot
2024-10-08 17:36 ` syzbot
2024-10-12 10:49 ` Muchun Song
2024-10-10 21:54 ` syzbot
2024-10-11 9:54 ` Vlastimil Babka
2025-09-04 3:36 ` 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=68b90923.050a0220.3db4df.020e.GAE@google.com \
--to=syzbot+7bb5e48f6ead66c72906@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mcgrof@kernel.org \
--cc=mhiramat@kernel.org \
--cc=mhocko@suse.com \
--cc=mike.kravetz@oracle.com \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@suse.cz \
/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