From: Eric Sandeen <sandeen@redhat.com>
To: Amerigo Wang <amwang@redhat.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
eteo@redhat.com, viro@zeniv.linux.org.uk, esandeen@redhat.com
Subject: Re: [Patch] allow file truncations when both suid and write permissions set
Date: Wed, 01 Jul 2009 13:12:08 -0500 [thread overview]
Message-ID: <4A4BA6F8.7090905@redhat.com> (raw)
In-Reply-To: <20090625090146.6616.9720.sendpatchset@localhost.localdomain>
Amerigo Wang wrote:
> When suid is set and the non-owner user has write permission,
> any writing into this file should be allowed and suid should be
> removed after that.
>
> However, current kernel only allows writing without truncations,
> when we do truncations on that file, we get EPERM. This is a bug.
Thanks, I'd noticed this once too but never put together a patch... :(
> Steps to reproduce this bug:
>
> % ls -l rootdir/file1
> -rwsrwsrwx 1 root root 3 Jun 25 15:42 rootdir/file1
> % echo h > rootdir/file1
> zsh: operation not permitted: rootdir/file1
> % ls -l rootdir/file1
> -rwsrwsrwx 1 root root 3 Jun 25 15:42 rootdir/file1
> % echo h >> rootdir/file1
> % ls -l rootdir/file1
> -rwxrwxrwx 1 root root 5 Jun 25 16:34 rootdir/file1
>
> This patch fixes it.
>
> (Need to Cc stable?)
probably a good idea.
> Signed-off-by: WANG Cong <amwang@redhat.com>
> Cc: Eric Sandeen <esandeen@redhat.com>
> Cc: Eugene Teo <eteo@redhat.com>
> Cc: Al Viro <viro@zeniv.linux.org.uk>
>
> ---
> diff --git a/fs/open.c b/fs/open.c
> index dd98e80..ebf6d8d 100644
> --- a/fs/open.c
> +++ b/fs/open.c
> @@ -199,7 +199,7 @@ out:
> int do_truncate(struct dentry *dentry, loff_t length, unsigned int time_attrs,
> struct file *filp)
> {
> - int err;
> + int ret;
> struct iattr newattrs;
>
> /* Not pretty: "inode->i_size" shouldn't really be signed. But it is. */
> @@ -214,12 +214,15 @@ int do_truncate(struct dentry *dentry, loff_t length, unsigned int time_attrs,
> }
>
> /* Remove suid/sgid on truncate too */
> - newattrs.ia_valid |= should_remove_suid(dentry);
> + ret = should_remove_suid(dentry);
> + newattrs.ia_valid |= ret;
> + if (ret)
> + newattrs.ia_valid |= ATTR_FORCE;
So I think the main problem here is simply that we didn't set
ATTR_FORCE, right...
Seems a little odd to |= with ret, -then- check if it's non-0. Maybe:
/* Remove suid/sgid on truncate too */
- newattrs.ia_valid |= should_remove_suid(dentry);
+ ret = should_remove_suid(dentry);
+ if (ret)
+ newattrs.ia_valid |= (ret | ATTR_FORCE);
?
Otherwise this much looks right to me, though I don't claim to be the
world's foremost expert at this. :)
Thanks,
-Eric
> mutex_lock(&dentry->d_inode->i_mutex);
> - err = notify_change(dentry, &newattrs);
> + ret = notify_change(dentry, &newattrs);
> mutex_unlock(&dentry->d_inode->i_mutex);
> - return err;
> + return ret;
> }
>
> static long do_sys_truncate(const char __user *pathname, loff_t length)
next prev parent reply other threads:[~2009-07-01 18:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-25 8:59 [Patch] allow file truncations when both suid and write permissions set Amerigo Wang
2009-07-01 18:12 ` Eric Sandeen [this message]
2009-07-01 19:27 ` Eric Sandeen
2009-07-01 19:29 ` Eric Paris
2009-07-01 20:15 ` Eric Paris
2009-07-02 10:14 ` Amerigo Wang
2009-07-02 12:12 ` Eric Paris
2009-07-03 10:02 ` Amerigo Wang
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=4A4BA6F8.7090905@redhat.com \
--to=sandeen@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=amwang@redhat.com \
--cc=esandeen@redhat.com \
--cc=eteo@redhat.com \
--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 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.