Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 27 Aug 2002 15:56:55 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 27 Aug 2002 15:56:54 -0400 Received: from tapu.f00f.org ([66.60.186.129]:39859 "EHLO tapu.f00f.org") by vger.kernel.org with ESMTP id ; Tue, 27 Aug 2002 15:56:51 -0400 Date: Tue, 27 Aug 2002 13:01:10 -0700 From: Chris Wedgwood To: Trond Myklebust Cc: Alan Cox , Thunder from the hill , Zheng Jian-Ming , linux-kernel@vger.kernel.org Subject: Re: problems with changing UID/GID Message-ID: <20020827200110.GB8985@tapu.f00f.org> References: <1030382219.1751.14.camel@irongate.swansea.linux.org.uk> <20020827075426.GA6696@tapu.f00f.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i X-No-Archive: Yes Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 591 Lines: 17 On Tue, Aug 27, 2002 at 09:35:10PM +0200, Trond Myklebust wrote: Locking does absolutely nothing for the problem of checking file access with one set of credentials, and then doing the subsequent file operation with another set of credentials. Can we not lock creds at the syscall level? Ick... shoot me for saying this :) --cw - 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/