From: Oscar Salvador <osalvador@suse.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: syzbot <syzbot+569ed13f4054f271087b@syzkaller.appspotmail.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
muchun.song@linux.dev, syzkaller-bugs@googlegroups.com,
Vivek Kasireddy <vivek.kasireddy@intel.com>
Subject: Re: [syzbot] [mm?] general protection fault in dequeue_hugetlb_folio_nodemask (2)
Date: Tue, 11 Jun 2024 19:46:33 +0200 [thread overview]
Message-ID: <ZmiNeTL5cZYmCbNf@localhost.localdomain> (raw)
In-Reply-To: <20240611103005.ae4170608bd15d63adee2492@linux-foundation.org>
On Tue, Jun 11, 2024 at 10:30:05AM -0700, Andrew Morton wrote:
> On Tue, 11 Jun 2024 03:34:25 -0700 syzbot <syzbot+569ed13f4054f271087b@syzkaller.appspotmail.com> wrote:
>
> > Hello,
> >
> > syzbot found the following issue on:
>
> Thanks.
>
> > Call Trace:
> > <TASK>
> > alloc_hugetlb_folio_nodemask+0xae/0x3f0 mm/hugetlb.c:2603
> > memfd_alloc_folio+0x15e/0x390 mm/memfd.c:75
> > memfd_pin_folios+0x1066/0x1720 mm/gup.c:3864
> > udmabuf_create+0x658/0x11c0 drivers/dma-buf/udmabuf.c:353
> > udmabuf_ioctl_create drivers/dma-buf/udmabuf.c:420 [inline]
> > udmabuf_ioctl+0x304/0x4f0 drivers/dma-buf/udmabuf.c:451
> > vfs_ioctl fs/ioctl.c:51 [inline]
> > __do_sys_ioctl fs/ioctl.c:907 [inline]
> > __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893
> > do_syscall_x64 arch/x86/entry/common.c:52 [inline]
> > do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
> > entry_SYSCALL_64_after_hwframe+0x77/0x7f
>
> I think we can pretty confidently point at the series "mm/gup:
> Introduce memfd_pin_folios() for pinning memfd folios". I'll drop the
> v14 series.
jfyi: I am trying to reproduce this locally.
--
Oscar Salvador
SUSE Labs
next prev parent reply other threads:[~2024-06-11 17:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 10:34 syzbot
2024-06-11 17:30 ` Andrew Morton
2024-06-11 17:46 ` Oscar Salvador [this message]
2024-06-11 17:52 ` Oscar Salvador
2024-06-12 5:11 ` Oscar Salvador
2024-06-12 5:55 ` Kasireddy, Vivek
2024-06-12 7:46 ` Oscar Salvador
2024-06-12 8:16 ` syzbot
2024-06-12 11:58 ` 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=ZmiNeTL5cZYmCbNf@localhost.localdomain \
--to=osalvador@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=syzbot+569ed13f4054f271087b@syzkaller.appspotmail.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