From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S269164AbUHZQRv (ORCPT ); Thu, 26 Aug 2004 12:17:51 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S269154AbUHZQRH (ORCPT ); Thu, 26 Aug 2004 12:17:07 -0400 Received: from verein.lst.de ([213.95.11.210]:17114 "EHLO mail.lst.de") by vger.kernel.org with ESMTP id S269128AbUHZQNO (ORCPT ); Thu, 26 Aug 2004 12:13:14 -0400 Date: Thu, 26 Aug 2004 18:13:03 +0200 From: Christoph Hellwig To: Jamie Lokier Cc: Christoph Hellwig , Hans Reiser , Alex Zarochentsev , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, Alexander Lyamin aka FLX , Linus Torvalds , ReiserFS List Subject: Re: silent semantic changes with reiser4 Message-ID: <20040826161303.GA4716@lst.de> Mail-Followup-To: Christoph Hellwig , Jamie Lokier , Hans Reiser , Alex Zarochentsev , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, Alexander Lyamin aka FLX , Linus Torvalds , ReiserFS List References: <20040824202521.GA26705@lst.de> <412CEE38.1080707@namesys.com> <20040825200859.GA16345@lst.de> <20040825203516.GB4688@backtop.namesys.com> <20040825205149.GA17654@lst.de> <412DA2CF.2030204@namesys.com> <20040826124119.GA431@lst.de> <20040826134812.GB5733@mail.shareable.org> <20040826155744.GA4250@lst.de> <20040826160638.GJ5733@mail.shareable.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040826160638.GJ5733@mail.shareable.org> User-Agent: Mutt/1.3.28i X-Spam-Score: -4.901 () BAYES_00 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Aug 26, 2004 at 05:06:38PM +0100, Jamie Lokier wrote: > Christoph Hellwig wrote: > > > There's bound to be some security issue, but I'm not sure what you're > > > getting at with /tmp. What sort of sort of security problem arises > > > with a world-writeable directory such as /tmp, that cannot arise with > > > the standard fs semantics? > > > > Actually you are right on that issue because it would open the > > device/fifo as directory and not device/fifo (in fact I'd had to look at > > the code again to see whether they actually do this only for files or > > also for special files) > > Are you saying that with reiser4, you can open a device or fifo with > O_DIRECTORY? That's what I thought, but as far as I can follow the code this is not actually true.