[lkml]   [2002]   [Apr]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [WTF] ->setattr() locking changes

> 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."

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:25    [W:0.021 / U:2.228 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site