From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Leon Hwang <leon.hwang@linux.dev>,
linux-mm@kvack.org, Muchun Song <muchun.song@linux.dev>,
Oscar Salvador <osalvador@suse.de>,
linux-kernel@vger.kernel.org, Lance Yang <lance.yang@linux.dev>
Subject: Re: [PATCH] hugetlb: add cond_resched() to __unmap_hugepage_range()
Date: Wed, 19 Aug 2026 09:53:25 +0200 [thread overview]
Message-ID: <35cca76a-4d3a-451a-b492-dd4423ac3e63@kernel.org> (raw)
In-Reply-To: <20260818115526.654d7311366b66cd031c67e4@linux-foundation.org>
On 8/18/26 20:55, Andrew Morton wrote:
> On Tue, 18 Aug 2026 20:21:37 +0200 "David Hildenbrand (Arm)" <david@kernel.org> wrote:
>
>>>
>>> That's pretty bad behavior and we might want to fix it in earlier
>>> kernels. Is PREEMPT_NONE effectively dead in 6.18.x and its
>>> existing users?
>>>
>>> If yes, we do want to fix older kernels then we should merge this.
>>>
>>
>> Okay, but that would be stable-only fixes?
>
> Not understanding.
>
> Maybe you refer to adding a patch to -stable but not to -linus? That's
> against the -stable rules
> (Documentation/process/stable-kernel-rules.rst).
It's tricky: if a problem only exists in stable (there is nothing to fix in
Linus' tree), then a stable-only fix is acceptable.
Otherwise we'd have to route unnecessary churn through upstream just for it to
reach stable, which doesn't make any sense.
When sending a stable patch, it should document how this is only a stable
problem and why no corresponding upstream fix is required (or how the actual fix
for upstream is actually deprecating the relevant config).
--
Cheers,
David
next prev parent reply other threads:[~2026-08-19 7:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 13:50 [PATCH] hugetlb: add cond_resched() to __unmap_hugepage_range() Leon Hwang
2026-08-18 14:23 ` David Hildenbrand (Arm)
2026-08-18 18:17 ` Andrew Morton
2026-08-18 18:21 ` David Hildenbrand (Arm)
2026-08-18 18:55 ` Andrew Morton
2026-08-18 22:18 ` Lance Yang
2026-08-18 23:24 ` Andrew Morton
2026-08-18 23:46 ` Matthew Wilcox
2026-08-18 23:59 ` Andrew Morton
2026-08-19 6:55 ` Michal Hocko
2026-08-19 7:53 ` David Hildenbrand (Arm) [this message]
2026-08-19 8:50 ` Michal Hocko
2026-08-19 8:54 ` David Hildenbrand (Arm)
2026-08-19 8:59 ` Michal Hocko
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=35cca76a-4d3a-451a-b492-dd4423ac3e63@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=lance.yang@linux.dev \
--cc=leon.hwang@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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.