linux-ext4 - Re: [fuse-devel] [PATCH 00/25] move handling of setuid/gid bits from VFS into individual setattr functions (RESEND)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20070809075502.b3426ce9.jlayton@redhat.com>
Date:	Thu, 9 Aug 2007 07:55:02 -0400
From:	Jeff Layton <jlayton@...hat.com>
To:	Jan Engelhardt <jengelh@...putergmbh.de>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	codalist@...EMANN.coda.cs.cmu.edu, cluster-devel@...hat.com,
	jfs-discussion@...ts.sourceforge.net,
	mikulas@...ax.karlin.mff.cuni.cz, reiserfs-devel@...r.kernel.org,
	zippel@...ux-m68k.org, xfs@....sgi.com,
	linux-kernel@...r.kernel.org, wli@...omorphy.com,
	joel.becker@...cle.com, dhowells@...hat.com,
	fuse-devel@...ts.sourceforge.net, jffs-dev@...s.com,
	user-mode-linux-user@...ts.sourceforge.net,
	linux-fsdevel@...r.kernel.org,
	v9fs-developer@...ts.sourceforge.net, linux-ext4@...r.kernel.org,
	linux-cifs-client@...ts.samba.org, ocfs2-devel@....oracle.com,
	bfennema@...con.csc.calpoly.edu
Subject: Re: [fuse-devel] [PATCH 00/25] move handling of setuid/gid bits
 from VFS into individual setattr functions (RESEND)

On Wed, 8 Aug 2007 22:05:13 +0200 (CEST)
Jan Engelhardt <jengelh@...putergmbh.de> wrote:

> 
> On Aug 8 2007 09:48, Andrew Morton wrote:
> >> > On Mon, 6 Aug 2007 09:54:03 -0400
> >> > Jeff Layton <jlayton@...hat.com> wrote:
> >> > 
> >> > Is there any way in which we can prevent these problems?  Say
> >> > 
> >> > - rename something so that unconverted filesystems will reliably fail to
> >> >   compile?
> >> > 
> >> 
> >> I suppose we could rename the .setattr inode operation to something
> >> else, but then we'll be stuck with it for at least a while. That seems
> >> sort of kludgey too...
> >
> >Sure.  We're changing the required behaviour of .setattr.  Changing its
> >name is a fine and reasonably reliable way to communicate that fact.
> 
> Maybe ->chattr/->chgattr?
> 
> 

That seems like a good replacement name. :-)

Now that I think on this further though, maybe Trond's suggestion to
change how the return code works is the best one. That would
(hopefully) catch this problem at runtime, so if someone is using a
precompiled but unconverted module then that would be detected too.

--
Jeff Layton <jlayton@...hat.com>
-
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html