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 for Android: free password hash cracker in your pocket

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

Date:	Thu, 10 May 2007 11:26:36 -0700
From:	Ulrich Drepper <drepper@...hat.com>
To:	Neil Brown <neilb@...e.de>
CC:	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] utimensat implementation

Ulrich Drepper wrote:
> Neil Brown wrote:
>> Does it also specify how to find out what granularity is used by the
>> filesystem?  I had a need for this just recently and couldn't see any
>> way to extract it.
> 
> That's still on the table.  We might end up with an fpathconf() solution.

OK, the pathconf()-based solution will most probably be in the next 
POSIX spec.

Now, somebody has to provide a way to get to this information.  The 
kernel does not export it so far.  Is it finally time to break down and 
allow pathconf() and fpathconf() syscalls into the kernel?

-- 
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
-
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/