From: Greg KH <gregkh@linuxfoundation.org>
To: Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org,
Pasha Tatashin <pasha.tatashin@soleen.com>,
Mike Rapoport <rppt@kernel.org>,
Pratyush Yadav <pratyush@kernel.org>,
Alexander Graf <graf@amazon.com>,
Christian Brauner <brauner@kernel.org>,
David Matlack <dmatlack@google.com>,
Jason Gunthorpe <jgg@ziepe.ca>, Jonathan Corbet <corbet@lwn.net>,
Masahiro Yamada <masahiroy@kernel.org>,
Miguel Ojeda <ojeda@kernel.org>,
Randy Dunlap <rdunlap@infradead.org>,
Samiullah Khawaja <skhawaja@google.com>,
Tejun Heo <tj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 6.17.y 2/4] kho: warn and fail on metadata or preserved memory in scratch area
Date: Thu, 27 Nov 2025 14:17:43 +0100 [thread overview]
Message-ID: <2025112728-shredding-amendment-79de@gregkh> (raw)
In-Reply-To: <20251122045222.2798582-2-sashal@kernel.org>
On Fri, Nov 21, 2025 at 11:52:20PM -0500, Sasha Levin wrote:
> From: Pasha Tatashin <pasha.tatashin@soleen.com>
>
> [ Upstream commit e38f65d317df1fd2dcafe614d9c537475ecf9992 ]
Oops, it's this one really that breaks the build, not patch 1/4.
thanks,
greg k-h
next prev parent reply other threads:[~2025-11-27 13:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-21 16:04 FAILED: patch "[PATCH] kho: allocate metadata directly from the buddy allocator" failed to apply to 6.17-stable tree gregkh
2025-11-22 4:52 ` [PATCH 6.17.y 1/4] kho: check if kho is finalized in __kho_preserve_order() Sasha Levin
2025-11-22 4:52 ` [PATCH 6.17.y 2/4] kho: warn and fail on metadata or preserved memory in scratch area Sasha Levin
2025-11-27 13:17 ` Greg KH [this message]
2025-11-22 4:52 ` [PATCH 6.17.y 3/4] kho: increase metadata bitmap size to PAGE_SIZE Sasha Levin
2025-11-22 4:52 ` [PATCH 6.17.y 4/4] kho: allocate metadata directly from the buddy allocator Sasha Levin
2025-11-27 13:15 ` [PATCH 6.17.y 1/4] kho: check if kho is finalized in __kho_preserve_order() Greg KH
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=2025112728-shredding-amendment-79de@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=corbet@lwn.net \
--cc=dmatlack@google.com \
--cc=graf@amazon.com \
--cc=jgg@ziepe.ca \
--cc=masahiroy@kernel.org \
--cc=ojeda@kernel.org \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@kernel.org \
--cc=rdunlap@infradead.org \
--cc=rppt@kernel.org \
--cc=sashal@kernel.org \
--cc=skhawaja@google.com \
--cc=stable@vger.kernel.org \
--cc=tj@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.