From: Sasha Levin <sashal@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: SeongJae Park <sj@kernel.org>,
"David Hildenbrand (Red Hat)" <david@kernel.org>,
"Ritesh Harjani (IBM)" <ritesh.list@gmail.com>,
Sourabh Jain <sourabhjain@linux.ibm.com>,
Borislav Petkov <bp@alien8.de>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Heiko Carstens <hca@linux.ibm.com>,
Ingo Molnar <mingo@redhat.com>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Muchun Song <muchun.song@linux.dev>,
Oscar Salvador <osalvador@suse.de>,
Thomas Gleixner <tglx@linutronix.de>,
Vasily Gorbik <gor@linux.ibm.com>,
linux-mm@kvack.org, linuxppc-dev@lists.ozlabs.org,
linux-s390@vger.kernel.org, x86@kernel.org,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6] mm/hugetlb: ignore hugepage kernel args if hugepages are unsupported
Date: Tue, 23 Dec 2025 12:11:51 -0500 [thread overview]
Message-ID: <aUrNVyuSaQrQLGZP@laps> (raw)
In-Reply-To: <20251223085434.a6d6ae08c3aedf420908f404@linux-foundation.org>
On Tue, Dec 23, 2025 at 08:54:34AM -0800, Andrew Morton wrote:
>On Tue, 23 Dec 2025 06:43:45 -0500 Sasha Levin <sashal@kernel.org> wrote:
>
>> >> > Yes, -stable maintainers have been asked to only backport patches where
>> >> > the MM developers asked for that, with cc:stable. There may be
>> >> > slipups, but as far as I know this is working.
>> >> >
>> >> > I don't actually know how they determine which patches need this
>> >> > special treatment. Pathname? Signed-off-by:akpm?
>> >>
>> >> I guess it is pathname, based on ignore_list file [1] of stable-queue repo.
>> >>
>> >> [1] https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/ignore_list#n16
>> >>
>> >
>> >Oh, that's a bit sad.
>> >
>> >- other trees sometimes mess with mm/ and they probably aren't aware
>> > that they need an explicit cc:stable.
>> >
>> >- misses drivers/block/zram and probably various other things that
>> > the MM team maintains.
>> >
>> >Oh well, I guess simple mm/* coverage is good enough. But I do worry a
>> >little that useful fixes coming into mm/ via other trees without
>> >cc:stable will get missed.
>>
>> How should we improve the filter? mm/ AND signed off by akpm?
>
>I think just signed-off-by:akpm please. That way, mm fixes which come
>in via other trees without cc:stable get backported.
Ack
>Obviously we'd prefer that such patches get appropriate consideration
>by the MM developers but sometimes other-tree people aren't that
>cooperative. In this case it's better to backport the thing rather
>than missing a fix?
I tend to err on the side of taking one extra thing rather than missing
something :)
Would you be interested in trying out AUTOSEL for mm/ again? In the current
workflow I give about 2-3 weeks for review, and all it takes to have a patch
dropped is to just reply with a "no".
I can generate a series with mm/ patches from v6.18..v6.19-rc2 that don't have
a Fixes/stable tag but the LLM thinks that it should be backported as a way for
you and other mm/ folk to gauge the current state of AUTOSEL, if that helps?
--
Thanks,
Sasha
WARNING: multiple messages have this Message-ID (diff)
From: Sasha Levin <sashal@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: SeongJae Park <sj@kernel.org>,
"David Hildenbrand (Red Hat)" <david@kernel.org>,
"Ritesh Harjani (IBM)" <ritesh.list@gmail.com>,
Sourabh Jain <sourabhjain@linux.ibm.com>,
Borislav Petkov <bp@alien8.de>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Heiko Carstens <hca@linux.ibm.com>,
Ingo Molnar <mingo@redhat.com>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Muchun Song <muchun.song@linux.dev>,
Oscar Salvador <osalvador@suse.de>,
Thomas Gleixner <tglx@linutronix.de>,
Vasily Gorbik <gor@linux.ibm.com>,
linux-mm@kvack.org, linuxppc-dev@lists.ozlabs.org,
linux-s390@vger.kernel.org, x86@kernel.org,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6] mm/hugetlb: ignore hugepage kernel args if hugepages are unsupported
Date: Tue, 23 Dec 2025 12:11:51 -0500 [thread overview]
Message-ID: <aUrNVyuSaQrQLGZP@laps> (raw)
In-Reply-To: <20251223085434.a6d6ae08c3aedf420908f404@linux-foundation.org>
On Tue, Dec 23, 2025 at 08:54:34AM -0800, Andrew Morton wrote:
>On Tue, 23 Dec 2025 06:43:45 -0500 Sasha Levin <sashal@kernel.org> wrote:
>
>> >> > Yes, -stable maintainers have been asked to only backport patches where
>> >> > the MM developers asked for that, with cc:stable. There may be
>> >> > slipups, but as far as I know this is working.
>> >> >
>> >> > I don't actually know how they determine which patches need this
>> >> > special treatment. Pathname? Signed-off-by:akpm?
>> >>
>> >> I guess it is pathname, based on ignore_list file [1] of stable-queue repo.
>> >>
>> >> [1] https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/ignore_list#n16
>> >>
>> >
>> >Oh, that's a bit sad.
>> >
>> >- other trees sometimes mess with mm/ and they probably aren't aware
>> > that they need an explicit cc:stable.
>> >
>> >- misses drivers/block/zram and probably various other things that
>> > the MM team maintains.
>> >
>> >Oh well, I guess simple mm/* coverage is good enough. But I do worry a
>> >little that useful fixes coming into mm/ via other trees without
>> >cc:stable will get missed.
>>
>> How should we improve the filter? mm/ AND signed off by akpm?
>
>I think just signed-off-by:akpm please. That way, mm fixes which come
>in via other trees without cc:stable get backported.
Ack
>Obviously we'd prefer that such patches get appropriate consideration
>by the MM developers but sometimes other-tree people aren't that
>cooperative. In this case it's better to backport the thing rather
>than missing a fix?
I tend to err on the side of taking one extra thing rather than missing
something :)
Would you be interested in trying out AUTOSEL for mm/ again? In the current
workflow I give about 2-3 weeks for review, and all it takes to have a patch
dropped is to just reply with a "no".
I can generate a series with mm/ patches from v6.18..v6.19-rc2 that don't have
a Fixes/stable tag but the LLM thinks that it should be backported as a way for
you and other mm/ folk to gauge the current state of AUTOSEL, if that helps?
--
Thanks,
Sasha
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2025-12-23 17:11 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-21 5:36 [PATCH v6] mm/hugetlb: ignore hugepage kernel args if hugepages are unsupported Sourabh Jain
2025-12-21 5:36 ` Sourabh Jain
2025-12-21 5:59 ` Ritesh Harjani
2025-12-21 5:59 ` Ritesh Harjani
2025-12-21 9:22 ` David Hildenbrand (Red Hat)
2025-12-21 9:22 ` David Hildenbrand (Red Hat)
2025-12-21 18:49 ` Andrew Morton
2025-12-21 18:49 ` Andrew Morton
2025-12-23 1:30 ` SeongJae Park
2025-12-23 1:30 ` SeongJae Park
2025-12-23 2:30 ` Andrew Morton
2025-12-23 2:30 ` Andrew Morton
2025-12-23 11:43 ` Sasha Levin
2025-12-23 11:43 ` Sasha Levin
2025-12-23 16:54 ` Andrew Morton
2025-12-23 16:54 ` Andrew Morton
2025-12-23 17:11 ` Sasha Levin [this message]
2025-12-23 17:11 ` Sasha Levin
2025-12-22 3:12 ` Ritesh Harjani
2025-12-22 3:12 ` Ritesh Harjani
2025-12-22 5:57 ` Sourabh Jain
2025-12-22 5:57 ` Sourabh Jain
2025-12-22 10:28 ` David Hildenbrand (Red Hat)
2025-12-22 10:28 ` David Hildenbrand (Red Hat)
2025-12-22 10:54 ` Christophe Leroy (CS GROUP)
2025-12-22 10:54 ` Christophe Leroy (CS GROUP)
2025-12-23 5:48 ` Sourabh Jain
2025-12-23 5:48 ` Sourabh Jain
2025-12-22 5:39 ` Sourabh Jain
2025-12-22 5:39 ` Sourabh Jain
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=aUrNVyuSaQrQLGZP@laps \
--to=sashal@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=christophe.leroy@csgroup.eu \
--cc=david@kernel.org \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-s390@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
--cc=ritesh.list@gmail.com \
--cc=sj@kernel.org \
--cc=sourabhjain@linux.ibm.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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.