From: Eric Biggers <ebiggers@kernel.org>
To: linux-fscrypt@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-mtd@lists.infradead.org
Subject: [PATCH v2 0/2] fscrypt: improve encrypted symlink performance
Date: Wed, 10 Apr 2019 13:21:13 -0700 [thread overview]
Message-ID: <20190410202115.64501-1-ebiggers@kernel.org> (raw)
This series improves the performance of following encrypted symlinks on
ext4, f2fs, and ubifs.
Eric Biggers (2):
vfs: use READ_ONCE() to access ->i_link
fscrypt: cache decrypted symlink target in ->i_link
fs/crypto/hooks.c | 40 +++++++++++++++++++++++++++++++++-------
fs/crypto/keyinfo.c | 21 +++++++++++++++++++++
fs/ext4/super.c | 3 +++
fs/f2fs/super.c | 3 +++
fs/namei.c | 4 ++--
fs/ubifs/super.c | 3 +++
include/linux/fscrypt.h | 5 +++++
7 files changed, 70 insertions(+), 9 deletions(-)
--
2.21.0.392.gf8f6787159e-goog
WARNING: multiple messages have this Message-ID (diff)
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: [PATCH v2 0/2] fscrypt: improve encrypted symlink performance
Date: Wed, 10 Apr 2019 13:21:13 -0700 [thread overview]
Message-ID: <20190410202115.64501-1-ebiggers@kernel.org> (raw)
This series improves the performance of following encrypted symlinks on
ext4, f2fs, and ubifs.
Eric Biggers (2):
vfs: use READ_ONCE() to access ->i_link
fscrypt: cache decrypted symlink target in ->i_link
fs/crypto/hooks.c | 40 +++++++++++++++++++++++++++++++++-------
fs/crypto/keyinfo.c | 21 +++++++++++++++++++++
fs/ext4/super.c | 3 +++
fs/f2fs/super.c | 3 +++
fs/namei.c | 4 ++--
fs/ubifs/super.c | 3 +++
include/linux/fscrypt.h | 5 +++++
7 files changed, 70 insertions(+), 9 deletions(-)
--
2.21.0.392.gf8f6787159e-goog
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next reply other threads:[~2019-04-10 20:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 20:21 Eric Biggers [this message]
2019-04-10 20:21 ` [PATCH v2 0/2] fscrypt: improve encrypted symlink performance Eric Biggers
2019-04-10 20:21 ` [f2fs-dev] [PATCH v2 1/2] vfs: use READ_ONCE() to access ->i_link Eric Biggers
2019-04-10 20:21 ` Eric Biggers
2019-04-10 20:21 ` Eric Biggers
2019-04-10 20:21 ` Eric Biggers
2019-04-10 21:06 ` Al Viro
2019-04-10 21:06 ` Al Viro
2019-04-10 21:06 ` Al Viro
2019-04-10 23:15 ` Eric Biggers
2019-04-10 23:15 ` Eric Biggers
2019-04-10 23:15 ` Eric Biggers
2019-04-11 2:25 ` Al Viro
2019-04-11 2:25 ` Al Viro
2019-04-11 2:25 ` Al Viro
2019-04-11 17:28 ` Eric Biggers
2019-04-11 17:28 ` Eric Biggers
2019-04-17 16:41 ` Theodore Ts'o
2019-04-17 16:41 ` Theodore Ts'o
2019-04-17 16:41 ` Theodore Ts'o
2019-04-10 20:21 ` [PATCH v2 2/2] fscrypt: cache decrypted symlink target in ->i_link Eric Biggers
2019-04-10 20:21 ` Eric Biggers
2019-04-10 20:21 ` Eric Biggers
2019-04-17 16:55 ` Theodore Ts'o
2019-04-17 16:55 ` Theodore Ts'o
2019-04-17 16:55 ` Theodore Ts'o
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=20190410202115.64501-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.