From: Lino Sanfilippo <LinoSanfilippo@gmx.de>
To: eparis@redhat.com
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
viro@zeniv.linux.org.uk
Subject: [PATCH] fanotify: if set by user unset FMODE_NONOTIFY before fsnotify_perm() is called
Date: Fri, 5 Nov 2010 17:05:27 +0100 [thread overview]
Message-ID: <20101105160527.GD24381@lsanfilippo.unix.rd.tt.avira.com> (raw)
Unsetting FMODE_NONOTIFY in fsnotify_open() is too late, since fsnotify_perm()
is called before. If FMODE_NONOTIFY is set fsnotify_perm() will skip permission
checks, so a user can still disable permission checks by setting this flag
in an open() call.
This patch corrects this by unsetting the flag before fsnotify_perm is called.
Signed-off-by: Lino Sanfilippo <LinoSanfilippo@gmx.de>
---
This patch applies against 2.6.37-rc1
It corrects this unsufficient fix
http://lkml.org/lkml/2010/10/29/125
I totally oversaw those fsnotify_perm() calls :(.
Hopefully this one will set things right...
diff -Nurp a/fs/namei.c b/fs/namei.c
--- a/fs/namei.c 2010-11-01 12:54:12.000000000 +0100
+++ b/fs/namei.c 2010-11-05 10:53:57.000000000 +0100
@@ -1748,6 +1748,9 @@ struct file *do_filp_open(int dfd, const
if (!(open_flag & O_CREAT))
mode = 0;
+ /* Must never be set by userspace */
+ open_flag &= ~FMODE_NONOTIFY;
+
/*
* O_SYNC is implemented as __O_SYNC|O_DSYNC. As many places only
* check for O_DSYNC if the need any syncing at all we enforce it's
diff -Nurp a/include/linux/fsnotify.h b/include/linux/fsnotify.h
--- a/include/linux/fsnotify.h 2010-11-01 12:54:12.000000000 +0100
+++ b/include/linux/fsnotify.h 2010-11-05 10:49:51.000000000 +0100
@@ -235,9 +235,6 @@ static inline void fsnotify_open(struct
if (S_ISDIR(inode->i_mode))
mask |= FS_ISDIR;
- /* FMODE_NONOTIFY must never be set from user */
- file->f_mode &= ~FMODE_NONOTIFY;
-
fsnotify_parent(path, NULL, mask);
fsnotify(inode, mask, path, FSNOTIFY_EVENT_PATH, NULL, 0);
}
reply other threads:[~2010-11-05 16:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20101105160527.GD24381@lsanfilippo.unix.rd.tt.avira.com \
--to=linosanfilippo@gmx.de \
--cc=eparis@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).