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:	Thu, 31 Jul 2014 19:22:53 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	basile@...nsource.dyc.edu
Cc:	linux-ext4@...r.kernel.org,
	"Anthony G. Basile" <blueness@...too.org>
Subject: Re: [PATCH] misc/e4defrag.c: use posix_fallocate64() if
 fallocate64() is unavailable

On Thu, Jul 31, 2014 at 02:07:48PM -0400, basile@...nsource.dyc.edu wrote:
> From: "Anthony G. Basile" <blueness@...too.org>
> 
> Commit 58229aaf removed the broken fallback syscall for fallocate64() on systems
> where the latter is unavailable.  However, it did not provide a substitute,
> so the build fails on uClibc which does not have fallocate64(), but does have
> posix_fallocate64().  Since fallocate64() is called with mode=0, we can make use
> of posix_fallocate64() on such systems.

The posix_fallocate[64]() is not the same as fallocate[64]().  Some
libc's will implement posix_fallocate() by brute force writing zeros
to the file.  Some will try calling the fallocate(2) system call if it
is present, and then fall back to the brute force write.  With
fallocate(2), if the file system returns ENOTSUPP, userspace gets told
about it.

So one question is how has uClibc actually implemented with
posix_fallocate[64]()?  Does it implement fallocate()?  I'd be happier
falling back to fallocate() and simply failing to support files which
are larger than the maximum size supported by off_t.

Yet another possibility is simply changing the Makefile to simply skip
building e4defrag if the C library doesn't support the fallocate
system call.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ