linux-ext4 - Re: [PATCH 6/6] tests: avoid spurious parallel failure due to temporary disk full

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-next>] [day] [month] [year] [list]

Date:	Mon, 04 Apr 2011 10:34:16 +0100
From:	Pádraig Brady <P@...igBrady.com>
To:	Jim Meyering <jim@...ering.net>
CC:	coreutils@....org, linux-ext4@...r.kernel.org
Subject: Re: [PATCH 6/6] tests: avoid spurious parallel failure due to temporary
 disk full

On 04/04/11 10:08, Jim Meyering wrote:
> Pádraig Brady wrote:
>> On 04/04/11 06:13, Jim Meyering wrote:
>>> From: Jim Meyering <meyering@...hat.com>
>>>
>>> Running the new fiemap-empty test uses 600MB of disk space via
>>> fallocate, and in so doing caused failure in unrelated tests that
>>> were running in parallel on a small file system.  Rather than
>>> simply running fallocate (which allocates the space, inducing
>>> disk full when it fails), skip the test if there is less than
>>> 800MB of free space, as computed via stat and awk.
> 
> Thanks for looking.
> 
>> Oops sorry.
>> Maybe worth noting is that stat works at a lower level,
> 
> Not sure what you mean?  Both use statfs.

Oops right. df uses f_bavail, so perhaps it might
be better to use %a rather than %f with `stat`?

This fallocate() behavior is annoying anyway,
as I'm not sure when it's useful, except for
filling up a file system.
It seems like a this would be useful.

#define FALLOC_FL_FULL_SIZE     0x03 /* allocate all or nothing */

cheers,
Pádraig.
--
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