Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Luiz Capitulino <luizcap@redhat.com>
To: Sasha Levin <sashal@kernel.org>,
	stable@vger.kernel.org, linux-mm@kvack.org
Cc: rppt@kernel.org, sayalip@linux.ibm.com
Subject: Re: [PATCH v6.18.y] selftests/mm: hugepage-mremap: fix mapping alignment
Date: Mon, 28 Sep 2026 09:08:48 -0400	[thread overview]
Message-ID: <7f58b9fe-8053-4068-89a1-ed217f62c9d1@redhat.com> (raw)
In-Reply-To: <2026-09-26-daily-reply-0004-re-hugepage-mremap-alignment-6-18-bounce@kernel.org>



On 9/26/26 11:26 AM, Sasha Levin wrote:
>> On upstream this was fixed by a914785f6349 ("selftests/mm: hugetlb-mremap:
>> add setup of HugeTLB pages") as that commit aligns 'length' to the
>> default HugeTLB page size as part of what it's doing. Since this commit
>> is part of a 50+ patch series, we backport only the 'length' alignment
>> bits to fix the test.
> 
> The change itself looks good, but the commit message has no upstream
> reference line. The SHA only appears in the prose and the subject differs
> from upstream, so the backport can't be matched to the upstream commit.
> 
> Could you send a v2 with
> 
>    commit a914785f6349da754e1226420bf4e51961956769 upstream.
> 
> as the first line of the body, with your explanation of the partial
> backport below it?

Yes, will do.

I was unsure if I should add it or not because this is not exactly a
backport, so I left it out. But I'm sending v2 with it now.

>>   2. This should apply to v6.12.y as well
> 
> 6.12 has the same failure, so please send the v2 for both 6.18.y and
> 6.12.y.

Will do.



      reply	other threads:[~2026-09-28 13:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-25 17:21 [PATCH v6.18.y] selftests/mm: hugepage-mremap: fix mapping alignment Luiz Capitulino
2026-09-26 15:26 ` Sasha Levin
2026-09-28 13:08   ` Luiz Capitulino [this message]

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=7f58b9fe-8053-4068-89a1-ed217f62c9d1@redhat.com \
    --to=luizcap@redhat.com \
    --cc=linux-mm@kvack.org \
    --cc=rppt@kernel.org \
    --cc=sashal@kernel.org \
    --cc=sayalip@linux.ibm.com \
    --cc=stable@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox