linux-ext4 - Re: Getting direct support for fallocate(2) into glibc

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]

Date:	Tue, 09 Dec 2008 12:03:55 -0600
From:	Eric Sandeen <sandeen@...hat.com>
To:	Theodore Tso <tytso@....EDU>
CC:	linux-ext4@...r.kernel.org
Subject: Re: Getting direct support for fallocate(2) into glibc

Theodore Tso wrote:
> On Tue, Dec 09, 2008 at 10:58:19AM -0600, Eric Sandeen wrote:
>> ... oh, ok, but plain old fallocate() isn't yet hooked up, odd.
>>
>> # gcc -o test-fallocate test-fallocate.c
>> /tmp/ccQTk6an.o: In function `main':
>> test-fallocate.c:(.text+0x3e): undefined reference to `fallocate'
>>
>> Especially odd because we have a man page shipping, but no actual
>> implemented interface  :)  OK, I'll go bug people.
> 
> Yep, that was what I was referring to.  We have the fallocate(2) man
> page because Michael Kerrisk has documented the userspace/kernel
> interface.  But that doesn't necessarily mean that glibc has wired up
> the interface.  (Sigh, we had been able to push this issue *before*
> glibc 2.9 shipped last month, but we were all too busy....)

Ok.  yeah, I honestly didn't realize that the bare interface wasn't
there.  :(

-Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html