From: syzbot <syzbot+1c6607097b258f18065c@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, brauner@kernel.org, jannh@google.com,
liam.howlett@oracle.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, lorenzo.stoakes@oracle.com,
mjguzik@gmail.com, oleg@redhat.com, pasha.tatashin@soleen.com,
pfalcato@suse.de, rostedt@goodmis.org,
syzkaller-bugs@googlegroups.com, vbabka@suse.cz
Subject: Re: [syzbot] [kernel?] INFO: task hung in exit_mm (5)
Date: Tue, 22 Jul 2025 09:22:04 -0700 [thread overview]
Message-ID: <687fbaac.a70a0220.21b99c.0010.GAE@google.com> (raw)
In-Reply-To: <4ca54a2c-46c8-435b-af72-7f871236eeb2@lucifer.local>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+1c6607097b258f18065c@syzkaller.appspotmail.com
Tested-by: syzbot+1c6607097b258f18065c@syzkaller.appspotmail.com
Tested on:
commit: b659a6dc selftests/damon: introduce _common.sh to host..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-unstable
console output: https://syzkaller.appspot.com/x/log.txt?x=171ecfd4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7e150e8ba2089ab9
dashboard link: https://syzkaller.appspot.com/bug?extid=1c6607097b258f18065c
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
prev parent reply other threads:[~2025-07-22 16:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 15:17 [syzbot] [kernel?] INFO: task hung in exit_mm (5) syzbot
2025-07-22 15:41 ` Lorenzo Stoakes
2025-07-22 16:22 ` 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=687fbaac.a70a0220.21b99c.0010.GAE@google.com \
--to=syzbot+1c6607097b258f18065c@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=jannh@google.com \
--cc=liam.howlett@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mjguzik@gmail.com \
--cc=oleg@redhat.com \
--cc=pasha.tatashin@soleen.com \
--cc=pfalcato@suse.de \
--cc=rostedt@goodmis.org \
--cc=syzkaller-bugs@googlegroups.com \
--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;
as well as URLs for NNTP newsgroup(s).