From: Andrew Morton <akpm@linux-foundation.org>
To: "Kasireddy, Vivek" <vivek.kasireddy@intel.com>
Cc: Anshuman Khandual <anshuman.khandual@arm.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"syzbot+a504cb5bae4fe117ba94@syzkaller.appspotmail.com"
<syzbot+a504cb5bae4fe117ba94@syzkaller.appspotmail.com>,
Steve Sistare <steven.sistare@oracle.com>,
Muchun Song <muchun.song@linux.dev>,
"David Hildenbrand" <david@redhat.com>,
Oscar Salvador <osalvador@suse.de>
Subject: Re: [PATCH] mm/hugetlb: Don't crash when allocating a folio if there are no resv
Date: Wed, 25 Jun 2025 13:46:52 -0700 [thread overview]
Message-ID: <20250625134652.b9184bb34e073bd7cb014844@linux-foundation.org> (raw)
In-Reply-To: <IA0PR11MB718542BC4FF75C1891803372F87BA@IA0PR11MB7185.namprd11.prod.outlook.com>
On Wed, 25 Jun 2025 14:18:28 +0000 "Kasireddy, Vivek" <vivek.kasireddy@intel.com> wrote:
> > Cool, thanks, I'll paste that into the changelog ;)
> >
> > So if this code path is rare but expected and normal, should we be
> > emitting this warning at all?
> I think it would be OK to drop the warning. Otherwise, Syzbot would continue
> to flag this issue.
OK. Could you please propose such a patch? With a fairly detailed
changelog explaining why the warning is bogus? After all, we don't
want to be removing our ability to detect a real bug!
next prev parent reply other threads:[~2025-06-25 20:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-18 5:28 Vivek Kasireddy
2025-06-18 6:44 ` Anshuman Khandual
2025-06-19 0:02 ` Andrew Morton
2025-06-19 5:30 ` Kasireddy, Vivek
2025-06-23 23:35 ` Andrew Morton
2025-06-25 14:18 ` Kasireddy, Vivek
2025-06-25 20:46 ` Andrew Morton [this message]
2025-06-19 13:53 ` Oscar Salvador
2025-06-21 2:02 ` 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=20250625134652.b9184bb34e073bd7cb014844@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=david@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
--cc=steven.sistare@oracle.com \
--cc=syzbot+a504cb5bae4fe117ba94@syzkaller.appspotmail.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