linux-ext4 - Re: BUG# ext4: getting call trace when copying large data to ext4 filesystem

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]

Date:	Thu, 21 Aug 2008 09:25:36 -0400
From:	Theodore Tso <tytso@....edu>
To:	Rishikesh K Rajak <risrajak@...ibm.com>
Cc:	linux-ext4@...r.kernel.org,
	"Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>
Subject: Re: BUG# ext4: getting call trace when copying large data to ext4
	filesystem

On Thu, Aug 21, 2008 at 03:12:52PM +0530, Rishikesh K Rajak wrote:
> 
> Wanted to know if anyone is getting the same problem too.
> 
> http://bugzilla.kernel.org/show_bug.cgi?id=11389

Yes, this was fixed quite a while ago; the patch is on the ext4 patch
queue.  Please note that if you are going to be doing extensive ext4
testing, you probably want to be using the latest ext4 patch sets.
The problem was first reported last week, and was fixed on the
linux-ext4 mailing list within two days, and we had a warning about
the problem on the Ext4 Wiki, on the Ext4 Howto page documenting the
problem, and telling people how to avoid it, or how to download the
specific patches from the ext4 patch queue.

Yesterday, I released the latest 2.6.26-ext4-7 patchset, which has
these problems fixed, and I updated the Ext4 Howto.

Regards,

						- 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