All of lore.kernel.org
 help / color / mirror / Atom feed
From: Amerigo Wang <amwang@redhat.com>
To: Eric Paris <eparis@redhat.com>
Cc: Eric Sandeen <sandeen@redhat.com>,
	linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	Eugene Teo <eteo@redhat.com>,
	viro@zeniv.linux.org.uk
Subject: Re: [Patch] allow file truncations when both suid and write  permissions set
Date: Fri, 03 Jul 2009 18:02:50 +0800	[thread overview]
Message-ID: <4A4DD74A.9050708@redhat.com> (raw)
In-Reply-To: <1246536739.22562.73.camel@dhcp235-23.rdu.redhat.com>

Eric Paris wrote:
> On Thu, 2009-07-02 at 18:14 +0800, Amerigo Wang wrote:
>   
>> Eric Paris wrote:
>>     
>>> So NAK on both Amerigo's and Eric's patch.  ATTR_FORCE is wrong.
>>> ATTR_FORCE here is going to force the security system to accept ALL of
>>> the attr changes, not just the ATTR_KILL_SUID and/or ATTR_KILL_SGID you
>>> |= in from should_remove_suid.
>>> You need to follow esandeen's recommendation, change file_remove_suid()
>>> to dentry_remove_suid() and then use dentry_remove_suid() in do_truncate
>>> instead of what you are currently trying to do (and I think that's
>>> supposed to be done under the i_mutex right?)
>>>   
>>>       
>> But file_remove_suid() actually adds ATTR_FORCE too, in __remove_suid()...
>>     
>
> The difference being that it adds it to a private ia_valid that ONLY
> contains the SUID/SGID bits that we need to force the removal of.  Not
> to the ia_valid that contains ATTR_SIZE and ATTR_FILE.
>   

Yeah! Got it. I will prepare a new patch...

Thank you!


      reply	other threads:[~2009-07-03 10:00 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
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 [this message]

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=4A4DD74A.9050708@redhat.com \
    --to=amwang@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=eparis@redhat.com \
    --cc=eteo@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --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.