linux-fscrypt.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: stable@vger.kernel.org
Cc: linux-fscrypt@vger.kernel.org
Subject: [PATCH 5.10 0/4] backport fscrypt symlink fixes to 5.10
Date: Wed,  1 Sep 2021 09:27:17 -0700	[thread overview]
Message-ID: <20210901162721.138605-1-ebiggers@kernel.org> (raw)

This series resolves some silent cherry-pick conflicts due to the
prototype of inode_operations::getattr having changed in v5.12, as well
as a conflict in the ubifs patch.  Please apply to 5.10-stable.

Eric Biggers (4):
  fscrypt: add fscrypt_symlink_getattr() for computing st_size
  ext4: report correct st_size for encrypted symlinks
  f2fs: report correct st_size for encrypted symlinks
  ubifs: report correct st_size for encrypted symlinks

 fs/crypto/hooks.c       | 44 +++++++++++++++++++++++++++++++++++++++++
 fs/ext4/symlink.c       | 11 ++++++++++-
 fs/f2fs/namei.c         | 11 ++++++++++-
 fs/ubifs/file.c         | 12 ++++++++++-
 include/linux/fscrypt.h |  7 +++++++
 5 files changed, 82 insertions(+), 3 deletions(-)

-- 
2.33.0


             reply	other threads:[~2021-09-01 16:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-01 16:27 Eric Biggers [this message]
2021-09-01 16:27 ` [PATCH 5.10 1/4] fscrypt: add fscrypt_symlink_getattr() for computing st_size Eric Biggers
2021-09-01 16:27 ` [PATCH 5.10 2/4] ext4: report correct st_size for encrypted symlinks Eric Biggers
2021-09-01 16:27 ` [PATCH 5.10 3/4] f2fs: " Eric Biggers
2021-09-01 16:27 ` [PATCH 5.10 4/4] ubifs: " Eric Biggers
2021-09-01 16:38 ` [PATCH 5.10 0/4] backport fscrypt symlink fixes to 5.10 Greg KH
2021-09-03 13:58   ` 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=20210901162721.138605-1-ebiggers@kernel.org \
    --to=ebiggers@kernel.org \
    --cc=linux-fscrypt@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;
as well as URLs for NNTP newsgroup(s).