From: syzbot <syzbot+f1d7fb4f94764243d23e@syzkaller.appspotmail.com>
To: airlied@redhat.com, akpm@linux-foundation.org, kraxel@redhat.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, muchun.song@linux.dev,
syzkaller-bugs@googlegroups.com, vivek.kasireddy@intel.com
Subject: Re: [syzbot] [fs?] [mm?] INFO: task hung in remove_inode_hugepages
Date: Tue, 09 Jul 2024 00:20:05 -0700 [thread overview]
Message-ID: <000000000000da3147061ccb5b55@google.com> (raw)
In-Reply-To: <IA0PR11MB7185EF69D19092412AC55B66F8DB2@IA0PR11MB7185.namprd11.prod.outlook.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+f1d7fb4f94764243d23e@syzkaller.appspotmail.com
Tested on:
commit: 581a87b1 fixup! mm/gup: introduce memfd_pin_folios() f..
git tree: https://gitlab.freedesktop.org/Vivek/drm-tip.git syzbot_fix_remove_inode
console output: https://syzkaller.appspot.com/x/log.txt?x=145a8535980000
kernel config: https://syzkaller.appspot.com/x/.config?x=409b5fcdf33b7555
dashboard link: https://syzkaller.appspot.com/bug?extid=f1d7fb4f94764243d23e
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2024-07-09 7:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-08 18:11 [syzbot] [fs?] [mm?] INFO: task hung in remove_inode_hugepages syzbot
2024-07-09 6:39 ` Kasireddy, Vivek
2024-07-09 7:20 ` syzbot [this message]
2024-07-09 21:36 ` Kasireddy, Vivek
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=000000000000da3147061ccb5b55@google.com \
--to=syzbot+f1d7fb4f94764243d23e@syzkaller.appspotmail.com \
--cc=airlied@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=kraxel@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vivek.kasireddy@intel.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;
as well as URLs for NNTP newsgroup(s).