From: Richard Weinberger <richard.weinberger@gmail.com>
To: Eric Biggers <ebiggers3@gmail.com>
Cc: linux-fscrypt@vger.kernel.org, Theodore Ts'o <tytso@mit.edu>,
Eric Biggers <ebiggers@google.com>,
linux-f2fs-devel@lists.sourceforge.net,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Jaegeuk Kim <jaegeuk@kernel.org>,
linux-ext4@vger.kernel.org
Subject: Re: [PATCH 3/4] ubifs: don't bother checking for encryption key in ->mmap()
Date: Tue, 23 May 2017 16:14:20 +0200 [thread overview]
Message-ID: <CAFLxGvxaiWFKH5L_BwPXGuG9PxA+0BkJ1qMvaDgAeVwBw+nCoQ@mail.gmail.com> (raw)
In-Reply-To: <20170523003945.14279-4-ebiggers3@gmail.com>
On Tue, May 23, 2017 at 2:39 AM, Eric Biggers <ebiggers3@gmail.com> wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> Since only an open file can be mmap'ed, and we only allow open()ing an
> encrypted file when its key is available, there is no need to check for
> the key again before permitting each mmap().
>
> Signed-off-by: Eric Biggers <ebiggers@google.com>
Acked-by: Richard Weinberger <richard@nod.at>
--
Thanks,
//richard
next prev parent reply other threads:[~2017-05-23 14:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 0:39 [PATCH 0/4] fscrypt: remove checks for encryption key after file open Eric Biggers
2017-05-23 0:39 ` [PATCH 1/4] ext4: don't bother checking for encryption key in ->mmap() Eric Biggers
2017-06-23 23:46 ` Theodore Ts'o
2017-06-23 23:46 ` Theodore Ts'o
2017-05-23 0:39 ` [PATCH 2/4] f2fs: " Eric Biggers
2017-05-23 0:39 ` Eric Biggers
2017-05-23 13:38 ` [f2fs-dev] " Chao Yu
2017-05-23 0:39 ` [PATCH 3/4] ubifs: " Eric Biggers
2017-05-23 0:39 ` Eric Biggers
2017-05-23 14:14 ` Richard Weinberger [this message]
2017-06-23 16:09 ` Theodore Ts'o
2017-06-23 17:18 ` Eric Biggers
2017-06-23 17:20 ` Richard Weinberger
2017-06-23 17:28 ` Theodore Ts'o
2017-06-23 17:28 ` Theodore Ts'o
2017-05-23 0:39 ` [PATCH 4/4] f2fs: don't bother checking for encryption key in ->write_iter() Eric Biggers
2017-05-23 0:39 ` Eric Biggers
2017-05-23 13:39 ` [f2fs-dev] " Chao Yu
2017-05-23 13:39 ` Chao Yu
2017-05-23 5:56 ` [PATCH 0/4] fscrypt: remove checks for encryption key after file open David Gstir
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=CAFLxGvxaiWFKH5L_BwPXGuG9PxA+0BkJ1qMvaDgAeVwBw+nCoQ@mail.gmail.com \
--to=richard.weinberger@gmail.com \
--cc=ebiggers3@gmail.com \
--cc=ebiggers@google.com \
--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-mtd@lists.infradead.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 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.