[Top] [All Lists]

Re: [PATCH 7/9] xfs: kill suid/sgid through the truncate path.

To: Ben Myers <bpm@xxxxxxx>
Subject: Re: [PATCH 7/9] xfs: kill suid/sgid through the truncate path.
From: Brian Foster <bfoster@xxxxxxxxxx>
Date: Thu, 30 May 2013 12:02:40 -0400
Cc: Dave Chinner <david@xxxxxxxxxxxxx>, xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <20130530155208.GD20028@xxxxxxx>
References: <1369636707-15150-1-git-send-email-david@xxxxxxxxxxxxx> <1369636707-15150-8-git-send-email-david@xxxxxxxxxxxxx> <51A75F7A.6040302@xxxxxxxxxx> <20130530155208.GD20028@xxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130514 Thunderbird/17.0.6
On 05/30/2013 11:52 AM, Ben Myers wrote:
> Hey Brian,
> On Thu, May 30, 2013 at 10:17:30AM -0400, Brian Foster wrote:
>> On 05/27/2013 02:38 AM, Dave Chinner wrote:
>>> From: Dave Chinner <dchinner@xxxxxxxxxx>
>>> XFS has failed to kill suid/sgid bits correctly when truncating
>>> files of non-zero size since commit c4ed4243 ("xfs: split
>>> xfs_setattr") introduced in the 3.1 kernel. Fix it.
>> The code makes sense and I can easily hit an assert when truncating
>> (extending) a suid file on a debug kernel without this patch (and I see
>> the suid dropped with the patch).
> What commands did you use?  It seems like this is dealing with S_ISGID, 
> correct?

Hi Ben,

Yeah, that confused me at first as well. I believe the vfs interprets
the ATTR_KILL_SUID/SGIT bits prior to the setattr call and wipes out the
associated mode bits if necessary.

What I did was basically create a zero sized file as root, chmod to a+s
and a+rwx and then as a regular user, truncate that file to something
larger than zero. Without the patch I hit the assert and with the patch
the assert doesn't fire and the setuid bit is dropped.


> Thanks,
>       Ben

<Prev in Thread] Current Thread [Next in Thread>