From: Yi Zhang <yi.zhang@redhat.com>
To: Hannes Reinecke <hare@suse.de>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block <linux-block@vger.kernel.org>,
"open list:NVM EXPRESS DRIVER" <linux-nvme@lists.infradead.org>,
Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
Daniel Wagner <dwagner@suse.de>, Ming Lei <ming.lei@redhat.com>,
linux-mm@kvack.org, muchun.song@linux.dev, osalvador@suse.de
Subject: Re: [bug report] kernel BUG at mm/hugetlb.c:5868! triggered by blktests nvme/tcp nvme/029
Date: Fri, 21 Nov 2025 18:32:20 +0800 [thread overview]
Message-ID: <CAHj4cs-mxgZ+tWXgOfjYx+X_bC35zBHyMbNYcCUuHe0JPLsHWw@mail.gmail.com> (raw)
In-Reply-To: <e281da57-caa0-4e36-8ff2-80175bc43090@suse.de>
[-- Attachment #1: Type: text/plain, Size: 961 bytes --]
On Fri, Nov 21, 2025 at 3:44 PM Hannes Reinecke <hare@suse.de> wrote:
> On 11/20/25 16:18, Yi Zhang wrote:
> > I did more testing today, and found that this issue cannot be
> > reproduced if I don't set the nr_hugepages
> >
> >
> https://github.com/linux-blktests/blktests/blob/master/tests/nvme/029#L71
> >
>
> But is the inverse also true, namely _can_ you reproduce it when
> nr_hugepages is set?
>
> Yes, it's now 100% reproduced in my environment.
CCed linux-mm@
> After all, there seems to be an issue with hugepages, so it's not
> surprising that we don't see it if we don't use hugepages...
>
> Cheers
>
> Hannes
> --
> Dr. Hannes Reinecke Kernel Storage Architect
> hare@suse.de +49 911 74053 688
> SUSE Software Solutions GmbH, Frankenstr. 146, 90461 Nürnberg
> HRB 36809 (AG Nürnberg), GF: I. Totev, A. McDonald, W. Knoblich
>
>
--
Best Regards,
Yi Zhang
[-- Attachment #2: Type: text/html, Size: 1900 bytes --]
parent reply other threads:[~2025-11-21 10:32 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <e281da57-caa0-4e36-8ff2-80175bc43090@suse.de>]
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=CAHj4cs-mxgZ+tWXgOfjYx+X_bC35zBHyMbNYcCUuHe0JPLsHWw@mail.gmail.com \
--to=yi.zhang@redhat.com \
--cc=axboe@kernel.dk \
--cc=dwagner@suse.de \
--cc=hare@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvme@lists.infradead.org \
--cc=ming.lei@redhat.com \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
--cc=shinichiro.kawasaki@wdc.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