From: syzbot <syzbot+a504cb5bae4fe117ba94@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, david@redhat.com,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, muchun.song@linux.dev,
steven.sistare@oracle.com, syzkaller-bugs@googlegroups.com,
vivek.kasireddy@intel.com
Subject: Re: [syzbot] [mm?] kernel BUG in alloc_hugetlb_folio_reserve
Date: Mon, 03 Feb 2025 11:25:03 -0800 [thread overview]
Message-ID: <67a1180f.050a0220.163cdc.004f.GAE@google.com> (raw)
In-Reply-To: <IA0PR11MB71859E012D110DCD92D7B179F8F52@IA0PR11MB7185.namprd11.prod.outlook.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+a504cb5bae4fe117ba94@syzkaller.appspotmail.com
Tested-by: syzbot+a504cb5bae4fe117ba94@syzkaller.appspotmail.com
Tested on:
commit: d1302efc selftests/udmabuf: add a test to pin first be..
git tree: https://gitlab.freedesktop.org/Vivek/drm-tip.git syzbot_fix_htlb_reserve_v2_rebase
console output: https://syzkaller.appspot.com/x/log.txt?x=114b75f8580000
kernel config: https://syzkaller.appspot.com/x/.config?x=3ed8e2f9a4233102
dashboard link: https://syzkaller.appspot.com/bug?extid=a504cb5bae4fe117ba94
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:[~2025-02-03 19:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-04 12:25 syzbot
2025-01-06 3:36 ` Muchun Song
2025-01-07 1:07 ` Kasireddy, Vivek
2025-01-07 1:07 ` syzbot
2025-02-01 20:51 ` syzbot
2025-02-02 4:51 ` Kasireddy, Vivek
2025-02-02 8:42 ` syzbot
2025-02-03 18:51 ` Kasireddy, Vivek
2025-02-03 19:25 ` syzbot [this message]
2025-02-02 17:27 ` syzbot
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=67a1180f.050a0220.163cdc.004f.GAE@google.com \
--to=syzbot+a504cb5bae4fe117ba94@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=steven.sistare@oracle.com \
--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