linux-kernel - Re: [PATCH] utimensat implementation

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]

Date:	Sun, 13 May 2007 22:02:26 +0100
From:	Christoph Hellwig <hch@...radead.org>
To:	Ulrich Drepper <drepper@...hat.com>
Cc:	Christoph Hellwig <hch@...radead.org>, Neil Brown <neilb@...e.de>,
	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] utimensat implementation

On Thu, May 10, 2007 at 12:44:19PM -0700, Ulrich Drepper wrote:
> Christoph Hellwig wrote:
> >E.g.
> >
> >long foofs_pathconf {
> >	[_PC_LINK_MAX]		= 16384,
> >	[_PC_2_SYMLINKS]	= 1,
> 
> In general I agree.  But what do you do for network filesystems?  Maybe 
> we'll have a network filesystem protocol which allows to query the 
> remote server about the underlying filesystem.  Then the return value is 
> dynamic and it's the maximum (coarsest granularity) of the network 
> filesystem itself and the underlying filesystem.

You're right, we'll probably want a method call for it.  The table
approach might still be a nice helper for the normal case.
-
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/