From: Eric Paris <eparis@redhat.com>
To: Amerigo Wang <amwang@redhat.com>
Cc: linux-kernel@vger.kernel.org, esandeen@redhat.com,
eteo@redhat.com, linux-fsdevel@vger.kernel.org,
akpm@linux-foundation.org, hirofumi@mail.parknet.co.jp,
viro@zeniv.linux.org.uk
Subject: Re: [Patch v3] vfs: allow file truncations when both suid and write permissions set
Date: Fri, 07 Aug 2009 15:57:05 -0400 [thread overview]
Message-ID: <1249675025.2694.15.camel@dhcp231-106.rdu.redhat.com> (raw)
In-Reply-To: <20090807100743.5822.90612.sendpatchset@localhost.localdomain>
On Fri, 2009-08-07 at 06:05 -0400, Amerigo Wang wrote:
> V2 -> V3:
> Call notify_change() before clearing suid/sgid.
> Thanks to OGAWA Hirofumi.
>
> V1 -> V2:
> Introduce dentry_remove_suid(), and use it in do_truncate().
> Thanks to Eric Paris.
>
>
> 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.
>
> 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.
>
> Signed-off-by: WANG Cong <amwang@redhat.com>
> Cc: Eric Sandeen <esandeen@redhat.com>
> Cc: Eric Paris <eparis@redhat.com>
> Cc: Eugene Teo <eteo@redhat.com>
> Cc: Al Viro <viro@zeniv.linux.org.uk>
> Cc: hirofumi@mail.parknet.co.jp
I was thinking about this and kept telling myself I was going to test v2
before I ack/nak. Clearly we shouldn't for the dropping of SUID if the
process didn't have permission to change the ATTR_SIZE.
Acked-by: Eric Paris <eparis@redhat.com>
next prev parent reply other threads:[~2009-08-07 19:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-07 10:05 [Patch v3] vfs: allow file truncations when both suid and write permissions set Amerigo Wang
2009-08-07 19:57 ` Eric Paris [this message]
2009-08-07 20:23 ` OGAWA Hirofumi
2009-08-07 20:38 ` Eric Paris
2009-08-07 20:53 ` OGAWA Hirofumi
2009-08-10 2:30 ` Amerigo Wang
2009-08-10 4:59 ` OGAWA Hirofumi
2009-08-10 11:49 ` Stephen Smalley
2009-08-10 12:43 ` OGAWA Hirofumi
2009-08-10 12:57 ` Stephen Smalley
2009-08-10 13:10 ` OGAWA Hirofumi
2009-08-12 9:03 ` 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=1249675025.2694.15.camel@dhcp231-106.rdu.redhat.com \
--to=eparis@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=amwang@redhat.com \
--cc=esandeen@redhat.com \
--cc=eteo@redhat.com \
--cc=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;
as well as URLs for NNTP newsgroup(s).