From: Eric Biggers <ebiggers@kernel.org>
To: linux-fscrypt@vger.kernel.org
Cc: linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-mtd@lists.infradead.org, linux-fsdevel@vger.kernel.org
Subject: [PATCH 0/5] fscrypt: report correct st_size for encrypted symlinks
Date: Thu, 1 Jul 2021 23:53:45 -0700 [thread overview]
Message-ID: <20210702065350.209646-1-ebiggers@kernel.org> (raw)
This series makes the stat() family of syscalls start reporting the
correct size for encrypted symlinks.
See patch 1 for a detailed explanation of the problem and solution.
Patch 1 adds a helper function that computes the correct size for an
encrypted symlink. Patches 2-4 make the filesystems with fscrypt
support use it, and patch 5 updates the documentation.
This series applies to mainline commit 3dbdb38e2869.
Eric Biggers (5):
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
fscrypt: remove mention of symlink st_size quirk from documentation
Documentation/filesystems/fscrypt.rst | 5 ---
fs/crypto/hooks.c | 44 +++++++++++++++++++++++++++
fs/ext4/symlink.c | 12 +++++++-
fs/f2fs/namei.c | 12 +++++++-
fs/ubifs/file.c | 13 +++++++-
include/linux/fscrypt.h | 7 +++++
6 files changed, 85 insertions(+), 8 deletions(-)
base-commit: 3dbdb38e286903ec220aaf1fb29a8d94297da246
--
2.32.0
WARNING: multiple messages have this Message-ID
From: Eric Biggers <ebiggers@kernel.org>
To: linux-fscrypt@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-mtd@lists.infradead.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [PATCH 0/5] fscrypt: report correct st_size for encrypted symlinks
Date: Thu, 1 Jul 2021 23:53:45 -0700 [thread overview]
Message-ID: <20210702065350.209646-1-ebiggers@kernel.org> (raw)
This series makes the stat() family of syscalls start reporting the
correct size for encrypted symlinks.
See patch 1 for a detailed explanation of the problem and solution.
Patch 1 adds a helper function that computes the correct size for an
encrypted symlink. Patches 2-4 make the filesystems with fscrypt
support use it, and patch 5 updates the documentation.
This series applies to mainline commit 3dbdb38e2869.
Eric Biggers (5):
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
fscrypt: remove mention of symlink st_size quirk from documentation
Documentation/filesystems/fscrypt.rst | 5 ---
fs/crypto/hooks.c | 44 +++++++++++++++++++++++++++
fs/ext4/symlink.c | 12 +++++++-
fs/f2fs/namei.c | 12 +++++++-
fs/ubifs/file.c | 13 +++++++-
include/linux/fscrypt.h | 7 +++++
6 files changed, 85 insertions(+), 8 deletions(-)
base-commit: 3dbdb38e286903ec220aaf1fb29a8d94297da246
--
2.32.0
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID
From: Eric Biggers <ebiggers@kernel.org>
To: linux-fscrypt@vger.kernel.org
Cc: linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-mtd@lists.infradead.org, linux-fsdevel@vger.kernel.org
Subject: [PATCH 0/5] fscrypt: report correct st_size for encrypted symlinks
Date: Thu, 1 Jul 2021 23:53:45 -0700 [thread overview]
Message-ID: <20210702065350.209646-1-ebiggers@kernel.org> (raw)
This series makes the stat() family of syscalls start reporting the
correct size for encrypted symlinks.
See patch 1 for a detailed explanation of the problem and solution.
Patch 1 adds a helper function that computes the correct size for an
encrypted symlink. Patches 2-4 make the filesystems with fscrypt
support use it, and patch 5 updates the documentation.
This series applies to mainline commit 3dbdb38e2869.
Eric Biggers (5):
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
fscrypt: remove mention of symlink st_size quirk from documentation
Documentation/filesystems/fscrypt.rst | 5 ---
fs/crypto/hooks.c | 44 +++++++++++++++++++++++++++
fs/ext4/symlink.c | 12 +++++++-
fs/f2fs/namei.c | 12 +++++++-
fs/ubifs/file.c | 13 +++++++-
include/linux/fscrypt.h | 7 +++++
6 files changed, 85 insertions(+), 8 deletions(-)
base-commit: 3dbdb38e286903ec220aaf1fb29a8d94297da246
--
2.32.0
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next reply other threads:[~2021-07-02 6:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-02 6:53 Eric Biggers [this message]
2021-07-02 6:53 ` [PATCH 0/5] fscrypt: report correct st_size for encrypted symlinks Eric Biggers
2021-07-02 6:53 ` [f2fs-dev] " Eric Biggers
2021-07-02 6:53 ` [PATCH 1/5] fscrypt: add fscrypt_symlink_getattr() for computing st_size Eric Biggers
2021-07-02 6:53 ` Eric Biggers
2021-07-02 6:53 ` [f2fs-dev] " Eric Biggers
2021-07-02 6:53 ` [PATCH 2/5] ext4: report correct st_size for encrypted symlinks Eric Biggers
2021-07-02 6:53 ` Eric Biggers
2021-07-02 6:53 ` [f2fs-dev] " Eric Biggers
2021-07-02 6:53 ` [PATCH 3/5] f2fs: " Eric Biggers
2021-07-02 6:53 ` Eric Biggers
2021-07-02 6:53 ` [f2fs-dev] " Eric Biggers
2021-07-02 6:53 ` [PATCH 4/5] ubifs: " Eric Biggers
2021-07-02 6:53 ` Eric Biggers
2021-07-02 6:53 ` [f2fs-dev] " Eric Biggers
2021-07-02 6:53 ` [PATCH 5/5] fscrypt: remove mention of symlink st_size quirk from documentation Eric Biggers
2021-07-02 6:53 ` Eric Biggers
2021-07-02 6:53 ` [f2fs-dev] " Eric Biggers
2021-07-26 3:58 ` [PATCH 0/5] fscrypt: report correct st_size for encrypted symlinks Eric Biggers
2021-07-26 3:58 ` Eric Biggers
2021-07-26 3:58 ` [f2fs-dev] " Eric Biggers
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=20210702065350.209646-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-fsdevel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.