linux-ext4 - Re: Fwd: Ext4 bug with fallocate

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]

Message-ID: <4ADB3AEC.8040901@redhat.com>
Date:	Sun, 18 Oct 2009 10:57:32 -0500
From:	Eric Sandeen <sandeen@...hat.com>
To:	Fredrik Andersson <nablaman@...il.com>
CC:	linux-ext4@...r.kernel.org
Subject: Re: Fwd: Ext4 bug with fallocate

Fredrik Andersson wrote:
> Hi, I'd like to report what I'm fairly certain is an ext4 bug. I hope
> this is the right place to do so.
> 
> My program creates a big file (around 30 GB) with posix_fallocate (to
> utilize extents), fills it with data and uses ftruncate to crop it to
> its final size (usually somewhere between 20 and 25 GB).
> The problem is that in around 5% of the cases, the program locks up
> completely in a syscall. The process can thus not be killed even with
> kill -9, and a reboot is all that will do.

does echo w > /proc/sysrq-trigger (this does sleeping processes; or use 
echo t for all processes) show you where the stuck threads are?

-Eric

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