linux-ext4 - Re: [PATCH] ext4: retry failed direct IO allocations

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

Message-ID: <20091003020436.GC11365@mit.edu>
Date:	Fri, 2 Oct 2009 22:04:36 -0400
From:	Theodore Tso <tytso@....edu>
To:	Eric Sandeen <sandeen@...hat.com>
Cc:	ext4 development <linux-ext4@...r.kernel.org>
Subject: Re: [PATCH] ext4: retry failed direct IO allocations

On Fri, Oct 02, 2009 at 05:39:11PM -0500, Eric Sandeen wrote:
> On a 256M filesystem, doing this in a loop:
>
>        xfs_io -F -f -d -c 'pwrite 0 64m' test
>        rm -f test
>
> eventually leads to ENOSPC.  (the xfs_io command does a
> 64m direct IO write to the file "test")
>
> As with other block allocation callers, it looks like we need to
> potentially retry the allocations on the initial ENOSPC.
>
> Signed-off-by: Eric Sandeen <sandeen@...hat.com>

Thanks, added to the ext4 patch queue.

						- 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