From: Greg KH <greg@kroah.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: stable@vger.kernel.org, linux-fscrypt@vger.kernel.org,
linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH 5.4 0/4] backport fscrypt symlink fixes to 5.4
Date: Fri, 3 Sep 2021 15:57:09 +0200 [thread overview]
Message-ID: <YTIptf2dFHf9sSIY@kroah.com> (raw)
In-Reply-To: <20210901164041.176238-1-ebiggers@kernel.org>
On Wed, Sep 01, 2021 at 09:40:37AM -0700, Eric Biggers wrote:
> This series backports some patches that failed to apply to 5.4-stable
> due to the prototype of inode_operations::getattr having changed in
> v5.12, as well several other conflicts. Please apply to 5.4-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
>
All now queued up, thanks.
greg k-h
prev parent reply other threads:[~2021-09-03 13:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-01 16:40 [PATCH 5.4 0/4] backport fscrypt symlink fixes to 5.4 Eric Biggers
2021-09-01 16:40 ` [PATCH 5.4 1/4] fscrypt: add fscrypt_symlink_getattr() for computing st_size Eric Biggers
2021-09-01 16:40 ` [PATCH 5.4 2/4] ext4: report correct st_size for encrypted symlinks Eric Biggers
2021-09-01 16:40 ` [PATCH 5.4 3/4] f2fs: " Eric Biggers
2021-09-01 16:40 ` [PATCH 5.4 4/4] ubifs: " Eric Biggers
2021-09-03 13:57 ` 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=YTIptf2dFHf9sSIY@kroah.com \
--to=greg@kroah.com \
--cc=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