From: Andrew Morton <akpm@linux-foundation.org>
To: Jann Horn <jannh@google.com>
Cc: Muchun Song <muchun.song@linux.dev>,
Oscar Salvador <osalvador@suse.de>,
linux-mm@kvack.org, Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Subject: Re: [PATCH] hugetlb: block hugetlb file creation if hugetlb is not set up
Date: Tue, 3 Jun 2025 19:54:52 -0700 [thread overview]
Message-ID: <20250603195452.d6238ea8a37caea9e727bc73@linux-foundation.org> (raw)
In-Reply-To: <CAG48ez0fQ5Ukg=0Scsv=N2k2jS=YRQpxLFeQRwMREABUr6yrgQ@mail.gmail.com>
On Tue, 3 Jun 2025 06:29:24 +0200 Jann Horn <jannh@google.com> wrote:
> I did think about whether this is the kind of borderline-breaking
> change that should include a pr_warn_once() to inform the user that
> their system encountered a specific behavioral difference due to a
> kernel change, in case it does unexpectedly break something; I decided
> against it, but if someone thinks this is sufficiently close to a
> breaking change to warrant that, I'll add that.
We could not make the change at this time. Instead we emit a loud
"don't do this, we're taking it away" warning and see if anyone reports
it.
Or we could merge this change as-is, along with a warning to get
people's attention then run that in -next for a while.
next prev parent reply other threads:[~2025-06-04 2:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-28 17:51 [PATCH] hugetlb: block hugetlb file creation if hugetlb is not set up Jann Horn
2025-06-03 3:41 ` Andrew Morton
2025-06-03 4:29 ` Jann Horn
2025-06-03 5:43 ` Oscar Salvador
2025-06-03 19:14 ` Jann Horn
2025-06-04 2:54 ` Andrew Morton [this message]
2025-06-16 22:09 ` Mark Brown
2025-06-17 9:13 ` David Hildenbrand
2025-06-17 15:35 ` Jann Horn
2025-06-17 8:12 ` [LTP] " kernel test robot
2025-06-17 8:12 ` kernel test robot
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=20250603195452.d6238ea8a37caea9e727bc73@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jannh@google.com \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.