This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/15661] posix_fallocate fallback code buggy and dangerous
- From: "carlos at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Wed, 03 Jun 2015 04:26:14 +0000
- Subject: [Bug libc/15661] posix_fallocate fallback code buggy and dangerous
- Auto-submitted: auto-generated
- References: <bug-15661-131 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=15661
--- Comment #9 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Rich Felker from comment #8)
> I think the XSH 2.9.7 justification is something of a cop-out, and the
> behavior is still undesirable/QoI-issue, but at least it's arguably
> conforming to the extent that applications should avoid depending on
> stricter behavior.
I agree with you, but I'm torn. There are definately applications that rely on
the fallback to work, and if we remove the fallback we'll have a ton of
applications doing the allocation loop themselves, likely getting the overflow
checking wrong, and the blocksize computation wrong. Therefore in the interest
of public safety it seems best to simply leave the loop in place.
--
You are receiving this mail because:
You are on the CC list for the bug.