From: Tyler Hicks <tyhicks@canonical.com>
To: Jann Horn <jann@thejh.net>, jeffm@suse.com
Cc: ecryptfs@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 2/2] ecryptfs: don't allow mmap when the lower fs doesn't support it
Date: Thu, 7 Jul 2016 18:22:05 -0500 [thread overview]
Message-ID: <577EE41D.6000900@canonical.com> (raw)
In-Reply-To: <20160705215740.GA14388@pc.thejh.net>
[-- Attachment #1.1: Type: text/plain, Size: 2219 bytes --]
On 07/05/2016 04:57 PM, Jann Horn wrote:
> On Tue, Jul 05, 2016 at 05:32:30PM -0400, jeffm@suse.com wrote:
>> From: Jeff Mahoney <jeffm@suse.com>
>>
>> There are legitimate reasons to disallow mmap on certain files, notably
>> in sysfs or procfs. We shouldn't emulate mmap support on file systems
>> that don't offer support natively.
>>
>> Signed-off-by: Jeff Mahoney <jeffm@suse.com>
>> ---
>> fs/ecryptfs/file.c | 16 +++++++++++++++-
>> 1 file changed, 15 insertions(+), 1 deletion(-)
>>
>> diff --git a/fs/ecryptfs/file.c b/fs/ecryptfs/file.c
>> index 7000b96..4aaa656 100644
>> --- a/fs/ecryptfs/file.c
>> +++ b/fs/ecryptfs/file.c
>> @@ -169,6 +169,20 @@ out:
>> return rc;
>> }
>>
>> +
>> +static int ecryptfs_mmap(struct file *file, struct vm_area_struct *vma)
>> +{
>> + struct dentry *dentry = ecryptfs_dentry_to_lower(file_dentry(file));
>> + /*
>> + * Don't allow mmap on top of file systems that don't support it
>> + * natively. If FILESYSTEM_MAX_STACK_DEPTH > 2 or ecryptfs
>> + * allows recursive mounting, this will need to be extended.
>
> Or if another new stacking filesystem appears whose f_op->mmap just forwards
> to lower_f_op->mmap - but thinking about it, in that scenario, my patch
> would stop working, too.
>
> At this point, I dislike both this patch and my own one because of their
> lack of robustness. Well, at least e54ad7f1ee263ffa5a2de9c609d58dfa27b21cd9
> should be solid. :/
I agree that neither approach provides long term protection from the
attack but they fix the immediate issue at hand. Therefore, I think we
need to move forward with what we have now.
Tyler
>
>
>> + */
>> + if (!d_inode(dentry)->i_fop->mmap)
>> + return -ENODEV;
>> + return generic_file_mmap(file, vma);
>> +}
>> +
>> /**
>> * ecryptfs_open
>> * @inode: inode speciying file to open
>> @@ -403,7 +417,7 @@ const struct file_operations ecryptfs_main_fops = {
>> #ifdef CONFIG_COMPAT
>> .compat_ioctl = ecryptfs_compat_ioctl,
>> #endif
>> - .mmap = generic_file_mmap,
>> + .mmap = ecryptfs_mmap,
>> .open = ecryptfs_open,
>> .flush = ecryptfs_flush,
>> .release = ecryptfs_release,
>> --
>> 2.7.1
>>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-07-07 23:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-05 21:32 [PATCH 1/2] Revert "ecryptfs: forbid opening files without mmap handler" jeffm
2016-07-05 21:32 ` [PATCH 2/2] ecryptfs: don't allow mmap when the lower fs doesn't support it jeffm
2016-07-05 21:57 ` Jann Horn
2016-07-07 23:22 ` Tyler Hicks [this message]
2016-07-07 23:20 ` Tyler Hicks
2016-07-08 0:46 ` Jeff Mahoney
2016-08-02 12:50 ` Henry Jensen
2016-08-02 13:05 ` Jeff Mahoney
2016-08-03 3:49 ` Greg KH
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=577EE41D.6000900@canonical.com \
--to=tyhicks@canonical.com \
--cc=ecryptfs@vger.kernel.org \
--cc=jann@thejh.net \
--cc=jeffm@suse.com \
--cc=stable@vger.kernel.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 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).