From: Eric Biggers <ebiggers@kernel.org>
To: stable@vger.kernel.org
Cc: linux-fscrypt@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-mtd@lists.infradead.org
Subject: [PATCH 0/4] backport fscrypt symlink fixes to 4.19
Date: Wed, 8 Sep 2021 14:50:29 -0700 [thread overview]
Message-ID: <20210908215033.1122580-1-ebiggers@kernel.org> (raw)
This series backports some patches that failed to apply to 4.19-stable
due to the prototype of inode_operations::getattr having changed in
v5.12, as well as several other conflicts. Please apply to 4.19-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_notsupp.h | 6 +++++
include/linux/fscrypt_supp.h | 1 +
6 files changed, 82 insertions(+), 3 deletions(-)
--
2.33.0.153.gba50c8fa24-goog
next reply other threads:[~2021-09-08 21:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 21:50 Eric Biggers [this message]
2021-09-08 21:50 ` [PATCH 1/4] fscrypt: add fscrypt_symlink_getattr() for computing st_size Eric Biggers
2021-09-08 21:50 ` [PATCH 2/4] ext4: report correct st_size for encrypted symlinks Eric Biggers
2021-09-08 21:50 ` [PATCH 3/4] f2fs: " Eric Biggers
2021-09-08 21:50 ` [PATCH 4/4] ubifs: " Eric Biggers
2021-09-13 9:33 ` [PATCH 0/4] backport fscrypt symlink fixes to 4.19 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=20210908215033.1122580-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-mtd@lists.infradead.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).