From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [PATCH] vfs: Fix use-after-free of vfsmount by mnt_drop_write()
Date: Tue, 23 Feb 2010 03:03:28 +0900 [thread overview]
Message-ID: <874ol9cfm7.fsf@devron.myhome.or.jp> (raw)
Hi,
Please review this. (This originally was for #untested branch, so this is
not minimal change perfectly.)
Those might be assuming that the nd->path.mnt refcnt is keeped by
filp after nameidata_to_filp().
It's wrong if nameidata_to_filp() returned the error. (nd->path and
filp are invalid)
Instead to use deep knowledge of nameidata_to_filp() internal, this
thinks the nd->path is invalid after nameidata_to_filp(). So, this
just take refcnt for mnt_want/drop_write().
Signed-off-by: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
---
fs/namei.c | 35 +++++++++++++++++++++++------------
1 file changed, 23 insertions(+), 12 deletions(-)
diff -puN fs/namei.c~nameidata_to_filp-mount-writer-fix fs/namei.c
--- linux-2.6/fs/namei.c~nameidata_to_filp-mount-writer-fix 2010-02-22 23:22:26.000000000 +0900
+++ linux-2.6-hirofumi/fs/namei.c 2010-02-22 23:59:34.000000000 +0900
@@ -1617,6 +1617,7 @@ struct file *do_filp_open(int dfd, const
struct path path;
struct dentry *dir;
int count = 0;
+ struct vfsmount *uninitialized_var(mnt_writer);
int will_truncate;
int flag = open_to_namei_flags(open_flag);
int force_reval = 0;
@@ -1733,16 +1734,20 @@ do_last:
* a permanent write count is taken through
* the 'struct file' in nameidata_to_filp().
*/
- error = mnt_want_write(nd.path.mnt);
+ mnt_writer = nd.path.mnt;
+ error = mnt_want_write(mnt_writer);
if (error)
goto exit_mutex_unlock;
error = __open_namei_create(&nd, &path, flag, mode);
if (error) {
- mnt_drop_write(nd.path.mnt);
+ mnt_drop_write(mnt_writer);
goto exit;
}
+ mntget(mnt_writer);
+ /* nd->path is invalid after this */
filp = nameidata_to_filp(&nd);
- mnt_drop_write(nd.path.mnt);
+ mnt_drop_write(mnt_writer);
+ mntput(mnt_writer);
if (nd.root.mnt)
path_put(&nd.root);
if (!IS_ERR(filp)) {
@@ -1794,16 +1799,20 @@ ok:
*/
will_truncate = open_will_truncate(flag, nd.path.dentry->d_inode);
if (will_truncate) {
- error = mnt_want_write(nd.path.mnt);
+ mnt_writer = nd.path.mnt;
+ error = mnt_want_write(mnt_writer);
if (error)
goto exit;
}
error = may_open(&nd.path, acc_mode, flag);
if (error) {
if (will_truncate)
- mnt_drop_write(nd.path.mnt);
+ mnt_drop_write(mnt_writer);
goto exit;
}
+ if (will_truncate)
+ mntget(mnt_writer);
+ /* nd->path is invalid after this */
filp = nameidata_to_filp(&nd);
if (!IS_ERR(filp)) {
error = ima_file_check(filp, acc_mode);
@@ -1814,10 +1823,10 @@ ok:
}
if (!IS_ERR(filp)) {
if (acc_mode & MAY_WRITE)
- vfs_dq_init(nd.path.dentry->d_inode);
+ vfs_dq_init(filp->f_path.dentry->d_inode);
if (will_truncate) {
- error = handle_truncate(&nd.path);
+ error = handle_truncate(&filp->f_path);
if (error) {
fput(filp);
filp = ERR_PTR(error);
@@ -1825,12 +1834,14 @@ ok:
}
}
/*
- * It is now safe to drop the mnt write
- * because the filp has had a write taken
- * on its behalf.
+ * It is now safe to drop the mnt write because the filp has
+ * had a write taken on its behalf. (NOTE: since O_TRUNC can
+ * be used with O_RDONLY, this needs to cover truncate path)
*/
- if (will_truncate)
- mnt_drop_write(nd.path.mnt);
+ if (will_truncate) {
+ mnt_drop_write(mnt_writer);
+ mntput(mnt_writer);
+ }
if (nd.root.mnt)
path_put(&nd.root);
return filp;
_
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next reply other threads:[~2010-02-22 18:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-22 18:03 OGAWA Hirofumi [this message]
2010-02-22 20:54 ` [PATCH] vfs: Fix use-after-free of vfsmount by mnt_drop_write() Valerie Aurora
2010-02-22 21:13 ` OGAWA Hirofumi
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=874ol9cfm7.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--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