Sure, I've attached my testcase (source and compiled for Barrier Breaker).
Matthias
On 09/01/2014 08:31 AM, Waldemar Brodkorb wrote:
Hi,
can you provide a simple testcase showing the bug?
best regards
Waldemar
Am 01.09.2014 um 00:53 schrieb Matthias Schiffer
Hi everyone,
I've written a patch to introduce fallocate()/fallocate64() in uclibc.
This is useful for e2fsprogs which now requires fallocate64(). [0]
Before sending the patch, here's some background: e2fsprogs was using a
direct syscall(__NR_fallocate, ...) in e4defrag which was broken [1].
Hi Anthony,
Anthony G. Basile wrote,
Hi everyone,
I've written a patch to introduce fallocate()/fallocate64() in
uclibc. This is useful for e2fsprogs which now requires
fallocate64(). [0]
Before sending the patch, here's some background: e2fsprogs was
using a direct
On 09/01/14 11:32, Waldemar Brodkorb wrote:
Hi Anthony,
Anthony G. Basile wrote,
Hi everyone,
I've written a patch to introduce fallocate()/fallocate64() in
uclibc. This is useful for e2fsprogs which now requires
fallocate64(). [0]
Before sending the patch, here's some background: e2fsprogs
Hi Anthony,
Anthony G. Basile wrote,
On 09/01/14 11:32, Waldemar Brodkorb wrote:
Hi Anthony,
Anthony G. Basile wrote,
Hi everyone,
I've written a patch to introduce fallocate()/fallocate64() in
uclibc. This is useful for e2fsprogs which now requires
fallocate64(). [0]
Before sending
Hi,
Waldemar Brodkorb wrote,
Hi Anthony,
Anthony G. Basile wrote,
On 09/01/14 11:32, Waldemar Brodkorb wrote:
Hi Anthony,
Anthony G. Basile wrote,
Hi everyone,
I've written a patch to introduce fallocate()/fallocate64() in
uclibc. This is useful for e2fsprogs which now
On 1 September 2014 19:59:49 CEST, Waldemar Brodkorb w...@openadk.org
Okay, solution is simple, sorry for not checking before mailing.
Test tries to allocate 4 GB, which is not available on my 128 MB
initramfs system
Bernhard: How could I disable this test for small devices?
$(shell df
On 2014/8/31 16:35, Waldemar Brodkorb wrote:
HI,
wangyufen wrote,
Called getpid() When creating a new process with clone(), getpid() returns
the father_process's value.
It should be child_process's value.
I think I see the same bug running the testsuite:
http://openadk.org/test/