From: Eric Biggers <ebiggers@kernel.org>
To: stable@vger.kernel.org
Cc: linux-ext4@vger.kernel.org
Subject: Please apply "ext4: don't allow journal inode to have encrypt flag" to 5.15 and earlier
Date: Sat, 7 Jan 2023 12:30:51 -0800 [thread overview]
Message-ID: <Y7nWexWBpMWKwdeB@sol.localdomain> (raw)
Please apply commit 105c78e12468 ("ext4: don't allow journal inode to have
encrypt flag") to the 5.15, 5.10, 5.4, and 4.19 LTS kernels, where it applies
cleanly.
It didn't get applied automatically because for the Fixes tag, I used a commit
in 5.18. However, that was the commit that exposed the problem, not the root
cause. IMO it makes sense to apply this to earlier kernels too, especially
because some people have backported the 5.18 commit.
- Eric
next reply other threads:[~2023-01-07 20:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-07 20:30 Eric Biggers [this message]
2023-01-10 15:48 ` Please apply "ext4: don't allow journal inode to have encrypt flag" to 5.15 and earlier 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=Y7nWexWBpMWKwdeB@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=linux-ext4@vger.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