Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 6 Apr 2002 15:24:48 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 6 Apr 2002 15:24:47 -0500 Received: from lightning.swansea.linux.org.uk ([194.168.151.1]:32273 "EHLO the-village.bc.nu") by vger.kernel.org with ESMTP id ; Sat, 6 Apr 2002 15:24:46 -0500 Subject: Re: [WTF] ->setattr() locking changes To: torvalds@transmeta.com (Linus Torvalds) Date: Sat, 6 Apr 2002 21:41:08 +0100 (BST) Cc: viro@math.psu.edu (Alexander Viro), trond.myklebust@fys.uio.no (Trond Myklebust), haveblue@us.ibm.com (Dave Hansen), linux-kernel@vger.kernel.org In-Reply-To: from "Linus Torvalds" at Apr 06, 2002 10:23:10 AM X-Mailer: ELM [version 2.5 PL6] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: From: Alan Cox Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@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. SuS v2 specifically says they may be cleared - 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/