public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Pratyush Yadav <pratyush@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Pratyush Yadav <pratyush@kernel.org>,
	 mm-commits@vger.kernel.org, surenb@google.com,
	 stable@vger.kernel.org,  rppt@kernel.org,
	pasha.tatashin@soleen.com,  graf@amazon.com,
	 ran.xiaokai@zte.com.cn
Subject: Re: [merged mm-hotfixes-stable] kho-init-alloc-tags-when-restoring-pages-from-reserved-memory.patch removed from -mm tree
Date: Wed, 21 Jan 2026 10:06:55 +0000	[thread overview]
Message-ID: <2vxzy0lrb7pc.fsf@kernel.org> (raw)
In-Reply-To: <20260120093639.3d316ff26f802b36bfe7a285@linux-foundation.org> (Andrew Morton's message of "Tue, 20 Jan 2026 09:36:39 -0800")

On Tue, Jan 20 2026, Andrew Morton wrote:

> On Tue, 20 Jan 2026 15:24:06 +0000 Pratyush Yadav <pratyush@kernel.org> wrote:
>
>> > The quilt patch titled
>> >      Subject: kho: init alloc tags when restoring pages from reserved memory
>> > has been removed from the -mm tree.  Its filename was
>> >      kho-init-alloc-tags-when-restoring-pages-from-reserved-memory.patch
>> >
>> > This patch was dropped because it was merged into the mm-hotfixes-stable branch
>> > of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
>> 
>> This patch isn't quite complete. See [0]. It doesn't do anything wrong,
>> it just doesn't fix the problem for every case.
>> 
>> I suggested a re-roll of this patch based on top of my cleanup patches
>> [1], since I think with those the end result is a bit nicer.
>> 
>> I suppose we have 3 options:
>> 
>> 1. Take this patch in hotfixes and leave kho_restore_pages() path
>>    unfixed. The fix the rest next merge window.
>> 
>> 2. Do a new version of this patch fixing kho_restore_pages() with the
>>    current code, and then re-roll the clean up series to fix conflicts
>>    for next merge window.
>> 
>> 3. Pull in the cleanups in hotfixes too, and then do a new revision of
>>    this patch on top.
>> 
>> I don't think the end result of option 2 is too horrible, so I think
>> that is probably the best option, but do let me know what you'd prefer.
>
> No probs, I removed this patch from mm-hotfixes-stable and put it back
> into mm-hotfixes-unstable, with a note that an updated version is expected.

Thanks.

Ran, would you be able to send a fixup soon? We are at -rc6 and it would
be great if this can land in 6.19. If not, then I can take it up.

-- 
Regards,
Pratyush Yadav

  reply	other threads:[~2026-01-21 10:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-19 20:30 [merged mm-hotfixes-stable] kho-init-alloc-tags-when-restoring-pages-from-reserved-memory.patch removed from -mm tree Andrew Morton
2026-01-20 15:24 ` Pratyush Yadav
2026-01-20 17:36   ` Andrew Morton
2026-01-21 10:06     ` Pratyush Yadav [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-01-27  2:57 Andrew Morton

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=2vxzy0lrb7pc.fsf@kernel.org \
    --to=pratyush@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=graf@amazon.com \
    --cc=mm-commits@vger.kernel.org \
    --cc=pasha.tatashin@soleen.com \
    --cc=ran.xiaokai@zte.com.cn \
    --cc=rppt@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=surenb@google.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