From: Eric Biggers <ebiggers@google.com>
To: linux-fsdevel@vger.kernel.org
Cc: linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, tytso@mit.edu,
jaegeuk@kernel.org
Subject: Re: [PATCH] fscrypto: move ioctl processing more fully into common code
Date: Tue, 22 Nov 2016 15:15:36 -0800 [thread overview]
Message-ID: <20161122231536.GA26438@google.com> (raw)
In-Reply-To: <1476723246-47420-1-git-send-email-ebiggers@google.com>
On Mon, Oct 17, 2016 at 09:54:06AM -0700, Eric Biggers wrote:
> Multiple bugs were recently fixed in the "set encryption policy" ioctl.
> To make it clear that fscrypt_process_policy() and fscrypt_get_policy()
> implement ioctls and therefore their implementations must take standard
> security and correctness precautions, rename them to
> fscrypt_ioctl_set_policy() and fscrypt_ioctl_get_policy(). Make the
> latter take in a struct file * to make it consistent with the former.
>
> In addition, make the common functions do the copies to and from
> userspace rather than duplicating this code within each filesystem, and
> memset the policy to 0 to make it clear there is no stack leak.
>
Ted, do you have any interest in taking this patch for 4.10?
Thanks,
Eric
next prev parent reply other threads:[~2016-11-22 23:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 16:54 [PATCH] fscrypto: move ioctl processing more fully into common code Eric Biggers
2016-10-17 16:54 ` Eric Biggers
2016-10-18 12:22 ` Richard Weinberger
2016-10-18 16:52 ` Eric Biggers
2016-11-22 23:15 ` Eric Biggers [this message]
2016-11-27 0:09 ` Theodore Ts'o
2016-11-27 0:09 ` Theodore Ts'o
2016-11-27 4:20 ` Eric Biggers
2016-11-27 4:20 ` Eric Biggers
2016-11-27 17:39 ` 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=20161122231536.GA26438@google.com \
--to=ebiggers@google.com \
--cc=jaegeuk@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@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 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.