All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fscrypt@vger.kernel.org, linux-ext4@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	Theodore Ts'o <tytso@mit.edu>, Jaegeuk Kim <jaegeuk@kernel.org>,
	Victor Hsieh <victorhsieh@google.com>
Subject: [GIT PULL] fsverity updates for 5.6
Date: Mon, 27 Jan 2020 17:49:44 -0800	[thread overview]
Message-ID: <20200128014944.GB960@sol.localdomain> (raw)

The following changes since commit fd6988496e79a6a4bdb514a4655d2920209eb85d:

  Linux 5.5-rc4 (2019-12-29 15:29:16 -0800)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/fs/fscrypt/fscrypt.git tags/fsverity-for-linus

for you to fetch changes up to da3a3da4e6c68459618a1043dcb12b450312a4e2:

  fs-verity: use u64_to_user_ptr() (2020-01-14 13:28:28 -0800)

----------------------------------------------------------------

- Optimize fs-verity sequential read performance by implementing
  readahead of Merkle tree pages.  This allows the Merkle tree to be
  read in larger chunks.

- Optimize FS_IOC_ENABLE_VERITY performance in the uncached case by
  implementing readahead of data pages.

- Allocate the hash requests from a mempool in order to eliminate the
  possibility of allocation failures during I/O.

----------------------------------------------------------------
Eric Biggers (4):
      fs-verity: implement readahead for FS_IOC_ENABLE_VERITY
      fs-verity: implement readahead of Merkle tree pages
      fs-verity: use mempool for hash requests
      fs-verity: use u64_to_user_ptr()

 fs/ext4/verity.c             | 47 ++++++++++++++++++++-
 fs/f2fs/data.c               |  2 +-
 fs/f2fs/f2fs.h               |  3 ++
 fs/f2fs/verity.c             | 47 ++++++++++++++++++++-
 fs/verity/enable.c           | 67 +++++++++++++++++++++++-------
 fs/verity/fsverity_private.h | 17 +++++---
 fs/verity/hash_algs.c        | 98 +++++++++++++++++++++++++++++++++-----------
 fs/verity/open.c             |  5 ++-
 fs/verity/verify.c           | 47 ++++++++++++++-------
 include/linux/fsverity.h     |  7 +++-
 10 files changed, 273 insertions(+), 67 deletions(-)


WARNING: multiple messages have this Message-ID (diff)
From: Eric Biggers <ebiggers@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Theodore Ts'o <tytso@mit.edu>,
	linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net,
	linux-fscrypt@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	Jaegeuk Kim <jaegeuk@kernel.org>,
	linux-ext4@vger.kernel.org, Victor Hsieh <victorhsieh@google.com>
Subject: [f2fs-dev] [GIT PULL] fsverity updates for 5.6
Date: Mon, 27 Jan 2020 17:49:44 -0800	[thread overview]
Message-ID: <20200128014944.GB960@sol.localdomain> (raw)

The following changes since commit fd6988496e79a6a4bdb514a4655d2920209eb85d:

  Linux 5.5-rc4 (2019-12-29 15:29:16 -0800)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/fs/fscrypt/fscrypt.git tags/fsverity-for-linus

for you to fetch changes up to da3a3da4e6c68459618a1043dcb12b450312a4e2:

  fs-verity: use u64_to_user_ptr() (2020-01-14 13:28:28 -0800)

----------------------------------------------------------------

- Optimize fs-verity sequential read performance by implementing
  readahead of Merkle tree pages.  This allows the Merkle tree to be
  read in larger chunks.

- Optimize FS_IOC_ENABLE_VERITY performance in the uncached case by
  implementing readahead of data pages.

- Allocate the hash requests from a mempool in order to eliminate the
  possibility of allocation failures during I/O.

----------------------------------------------------------------
Eric Biggers (4):
      fs-verity: implement readahead for FS_IOC_ENABLE_VERITY
      fs-verity: implement readahead of Merkle tree pages
      fs-verity: use mempool for hash requests
      fs-verity: use u64_to_user_ptr()

 fs/ext4/verity.c             | 47 ++++++++++++++++++++-
 fs/f2fs/data.c               |  2 +-
 fs/f2fs/f2fs.h               |  3 ++
 fs/f2fs/verity.c             | 47 ++++++++++++++++++++-
 fs/verity/enable.c           | 67 +++++++++++++++++++++++-------
 fs/verity/fsverity_private.h | 17 +++++---
 fs/verity/hash_algs.c        | 98 +++++++++++++++++++++++++++++++++-----------
 fs/verity/open.c             |  5 ++-
 fs/verity/verify.c           | 47 ++++++++++++++-------
 include/linux/fsverity.h     |  7 +++-
 10 files changed, 273 insertions(+), 67 deletions(-)



_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

             reply	other threads:[~2020-01-28  1:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-28  1:49 Eric Biggers [this message]
2020-01-28  1:49 ` [f2fs-dev] [GIT PULL] fsverity updates for 5.6 Eric Biggers
2020-01-28 23:40 ` pr-tracker-bot
2020-01-28 23:40   ` [f2fs-dev] " pr-tracker-bot

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=20200128014944.GB960@sol.localdomain \
    --to=ebiggers@kernel.org \
    --cc=jaegeuk@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-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=tytso@mit.edu \
    --cc=victorhsieh@google.com \
    /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.