linux-kernel - Re: [PATCH] vfs: Pass setxattr(2) flags properly

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: <BANLkTi=cTOrww+K4R3=0OAYtQYd3vmpvYw@mail.gmail.com>
Date:	Wed, 20 Apr 2011 20:58:35 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Christoph Hellwig <hch@....de>
Cc:	Jan Kara <jack@...e.cz>, LKML <linux-kernel@...r.kernel.org>,
	linux-fsdevel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Al Viro <viro@...iv.linux.org.uk>
Subject: Re: [PATCH] vfs: Pass setxattr(2) flags properly

On Wed, Apr 20, 2011 at 8:09 PM, Christoph Hellwig <hch@....de> wrote:
>
> It's not really used very much.  The only use of XATTR_CREATE is to
> prevent creating the attrs used for ACLs from the normal xattrs
> interface instead of going through the ACL code, and XATTR_REPLACE
> is only used to return -ENOATTR when it's set but the attribute
> actually is empty.
>
> The first one could probably be used (by root) to create invalid
> attrs that confuse the ACL code, and the second may confuse application
> using it, although I doubt there are many.

Ok.

So nobody much i going to care. But I presume that you ack the patch
itself as correct?

                      Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/