public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Eric Biggers <ebiggers@kernel.org>
Cc: stable@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: Please apply "ext4: don't allow journal inode to have encrypt flag" to 5.15 and earlier
Date: Tue, 10 Jan 2023 16:48:35 +0100	[thread overview]
Message-ID: <Y72I0/KixO+WoKsc@kroah.com> (raw)
In-Reply-To: <Y7nWexWBpMWKwdeB@sol.localdomain>

On Sat, Jan 07, 2023 at 12:30:51PM -0800, Eric Biggers wrote:
> 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.

All now queued up, thanks.

greg k-h

      reply	other threads:[~2023-01-10 15:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-07 20:30 Please apply "ext4: don't allow journal inode to have encrypt flag" to 5.15 and earlier Eric Biggers
2023-01-10 15:48 ` Greg KH [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=Y72I0/KixO+WoKsc@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=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