From: Eric Biggers <ebiggers@kernel.org>
To: Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 6.18.y] fscrypt: Fix key setup in edge case with multiple data unit sizes
Date: Thu, 2 Jul 2026 15:42:29 -0700 [thread overview]
Message-ID: <20260702224229.GA116181@quark> (raw)
In-Reply-To: <20260702222323.3702129-1-sashal@kernel.org>
On Thu, Jul 02, 2026 at 06:23:23PM -0400, Sasha Levin wrote:
> [ added explicit GFP_KERNEL argument to kzalloc_obj() since the 6.18 macro lacks the variadic default-gfp form ]
> Signed-off-by: Sasha Levin <sashal@kernel.org>
At this point I just have to nack any patch that isn't Cc'ed to the
subsystem mailing list and isn't a clean cherry-pick. I always mention
to include the mailing list, but clearly that's not working, as I just
get ignored.
Nacked-by: Eric Biggers <ebiggers@kernel.org>
It would also be a good idea to make k[mz]alloc_obj() on 6.18 have the
same behavior as on mainline, as every patch using those is going to
have the same issue.
- Eric
prev parent reply other threads:[~2026-07-02 22:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 13:29 FAILED: patch "[PATCH] fscrypt: Fix key setup in edge case with multiple data unit" failed to apply to 6.18-stable tree gregkh
2026-07-02 22:23 ` [PATCH 6.18.y] fscrypt: Fix key setup in edge case with multiple data unit sizes Sasha Levin
2026-07-02 22:42 ` Eric Biggers [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=20260702224229.GA116181@quark \
--to=ebiggers@kernel.org \
--cc=sashal@kernel.org \
--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