From: Andries.Brouwer@cwi.nl
Date: Sat, 6 Apr 2002 18:45:11 GMT
Message-Id: <UTC200204061845.SAA545386.aeb@cwi.nl>
To: torvalds@transmeta.com, viro@math.psu.edu
Subject: Re: [WTF] ->setattr() locking changes
Cc: haveblue@us.ibm.com, linux-kernel@vger.kernel.org,
        trond.myklebust@fys.uio.no
Sender: linux-kernel-owner@vger.kernel.org


    > Hmm...  While we are at it, why don't we remove suid/sgid on truncate(2)?

    Are there any standards saying either way? But yes, it sounds logical.

"This function shall not modify the file offset for any open file
 descriptions associated with the file. Upon successful completion,
 if the file size is changed, this function shall mark for update
 the st_ctime and st_mtime fields of the file, and the S_ISUID and
 S_ISGID bits of the file mode may be cleared."

Andries
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/