linux-ext4 - Re: Please apply "ext4: don't allow journal inode to have encrypt flag" to 5.15 and earlier

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <Y72I0/KixO+WoKsc@kroah.com>
Date:   Tue, 10 Jan 2023 16:48:35 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Eric Biggers <ebiggers@...nel.org>
Cc:     stable@...r.kernel.org, linux-ext4@...r.kernel.org
Subject: Re: Please apply "ext4: don't allow journal inode to have encrypt
 flag" to 5.15 and earlier

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