linux-kernel - Re: [patch 1/4] vfs: utimes: move owner check into inode_change

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] [day] [month] [year] [list]

Message-Id: <E1KDglP-0005Rx-Fh@pomaz-ex.szeredi.hu>
Date:	Tue, 01 Jul 2008 16:23:23 +0200
From:	Miklos Szeredi <miklos@...redi.hu>
To:	mtk.manpages@...glemail.com
CC:	miklos@...redi.hu, viro@...iv.linux.org.uk,
	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	hch@...radead.org, akpm@...ux-foundation.org, drepper@...hat.com,
	mtk.manpages@...il.com
Subject: Re: [patch 1/4] vfs: utimes: move owner check into inode_change_ok()

Hi Michael,

On Tue, 1 Jul 2008, Michael Kerrisk wrote:
> On Tue, Jul 1, 2008 at 3:01 PM, Miklos Szeredi <miklos@...redi.hu> wrote:
> > From: Miklos Szeredi <mszeredi@...e.cz>
> >
> > Add a new ia_valid flag: ATTR_TIMES_SET, to handle the
> > UTIMES_OMIT/UTIMES_NOW and UTIMES_NOW/UTIMES_OMIT cases.  In these
> > cases neither ATTR_MTIME_SET nor ATTR_ATIME_SET is in the flags, yet
> > the POSIX draft specifies that permission checking is performed the
> > same way as if one or both of the times was explicitly set to a
> > timestamp.
> >
> > See the path "vfs: utimensat(): fix error checking for
> > {UTIME_NOW,UTIME_OMIT} case" by Michael Kerrisk for the patch
> > introducing this behavior.
> >
> > This is a cleanup, as well as allowing filesystems (NFS/fuse/...) to
> > perform their own permission checking instead of the default.
> 
> What kernel version/tree is this patch against?

Against latest git.  2.6.26-rc8-git2 seems to be recent enough.

Miklos
--
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/