linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Satya Tangirala <satyat@google.com>
To: "Theodore Y . Ts'o" <tytso@mit.edu>,
	Jaegeuk Kim <jaegeuk@kernel.org>,
	Eric Biggers <ebiggers@kernel.org>, Chao Yu <chao@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-fscrypt@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH v2 2/3] fscrypt: Add metadata encryption support
Date: Thu, 24 Dec 2020 11:31:39 +0000	[thread overview]
Message-ID: <X+R8G5/Htwau2b34@google.com> (raw)
In-Reply-To: <20201217150435.1505269-3-satyat@google.com>

I realized I didn't update fscrypt_mergeable_bio() to take metadata
encryption into account, so bios will be more fragmented than required.
I'll fix it in v3.

  parent reply	other threads:[~2020-12-24 11:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-17 15:04 [PATCH v2 0/3] add support for metadata encryption to F2FS Satya Tangirala
2020-12-17 15:04 ` [PATCH v2 1/3] fscrypt, f2fs: replace fscrypt_get_devices with fscrypt_get_device Satya Tangirala
2020-12-17 15:04 ` [PATCH v2 2/3] fscrypt: Add metadata encryption support Satya Tangirala
2020-12-17 15:24   ` Satya Tangirala
2020-12-24 11:31   ` Satya Tangirala [this message]
2021-01-29 20:41   ` Eric Biggers
2020-12-17 15:04 ` [PATCH v2 3/3] f2fs: " Satya Tangirala
2021-01-29 20:57   ` Eric Biggers
2020-12-17 15:16 ` [PATCH v2 0/3] add support for metadata encryption to F2FS Satya Tangirala
2020-12-17 18:08 ` Theodore Y. Ts'o
2020-12-17 20:51   ` Satya Tangirala
2020-12-17 23:34     ` Theodore Y. Ts'o
2020-12-18  0:05       ` Satya Tangirala

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=X+R8G5/Htwau2b34@google.com \
    --to=satyat@google.com \
    --cc=chao@kernel.org \
    --cc=ebiggers@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-fscrypt@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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).