linux-kernel - Re: [PATCH 3/3] lutimesat: actual syscall and wire-up on i386

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: <20070129160250.GA6021@localhost.sw.ru>
Date:	Mon, 29 Jan 2007 19:02:50 +0300
From:	Alexey Dobriyan <adobriyan@...nvz.org>
To:	Ulrich Drepper <drepper@...hat.com>
Cc:	Andrew Morton <akpm@...l.org>, devel@...nvz.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/3] lutimesat: actual syscall and wire-up on i386

On Mon, Jan 29, 2007 at 07:07:04AM -0800, Ulrich Drepper wrote:
> Alexey Dobriyan wrote:
> > What do you mean by "filesystems cannot support lutimes"? Filesystems
> > that don't have on-disk timestamps for symlinks?
> 
> Yes.

Checked to be sure, on ext2, ext3, reiserfs, XFS symlink timestamps
stick across mounts/umounts.

Also, looking at disk inode structures of UFS, SysV, JFFS2, GFS2, EFS, I
think they should handle lutimesat(2) just fine.

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