Linux EXT4 FS development
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fscrypt@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-ext4@vger.kernel.org, Theodore Ts'o <tytso@mit.edu>,
	Jaegeuk Kim <jaegeuk@kernel.org>,
	Alberto Garcia <berto@igalia.com>,
	Baokun Li <libaokun@linux.alibaba.com>
Subject: [GIT PULL] fscrypt fixes for v7.4-rc1
Date: Thu, 29 Oct 2026 10:06:15 -0700	[thread overview]
Message-ID: <20261029170615.GA1862@quark> (raw)

The following changes since commit 5b0764a53235d3c77e1ed674e836e1b3fe1a4b1f:

  Merge tag 'drm-next-2026-10-21' of https://gitlab.freedesktop.org/drm/kernel (2026-10-23 18:29:02 -1000)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/fs/fscrypt/linux.git tags/fscrypt-for-linus

for you to fetch changes up to a5e894bc87b76fd980075892ba77e6bdeeb5e4d0:

  ext4: reject encrypted inodes when block size > page size (2026-10-24 12:58:37 -0700)

----------------------------------------------------------------

- Add more checks to prevent encryption on "large block size" ext4
  filesystems (s_blocksize > PAGE_SIZE), which isn't supported yet.
  There was already a mount-time check, but it wasn't enough.

- Add missing memory barrier to fscrypt_find_mode_key()

- Add missing zeroization in an error path

----------------------------------------------------------------
Alberto Garcia (2):
      ext4: refuse encryption when block size > page size
      ext4: reject encrypted inodes when block size > page size

Baokun Li (1):
      fscrypt: Fix missing barrier in fscrypt_find_mode_key()

Eric Biggers (1):
      fscrypt: Explicitly zeroize sw_secret in error path

 fs/crypto/keyring.c  | 4 +++-
 fs/crypto/keysetup.c | 8 +++++++-
 fs/ext4/crypto.c     | 9 +++++++++
 fs/ext4/inode.c      | 6 ++++++
 4 files changed, 25 insertions(+), 2 deletions(-)

                 reply	other threads:[~2026-10-29 17:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20261029170615.GA1862@quark \
    --to=ebiggers@kernel.org \
    --cc=berto@igalia.com \
    --cc=jaegeuk@kernel.org \
    --cc=libaokun@linux.alibaba.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fscrypt@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=tytso@mit.edu \
    /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