linux-ext4 - Re: [next-20101038] Call trace in ext4

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]

Date:	Thu, 28 Oct 2010 17:06:44 -0400
From:	Ted Ts'o <tytso@....edu>
To:	sedat.dilek@...il.com
Cc:	Markus Trippelsdorf <markus@...ppelsdorf.de>,
	LKML <linux-kernel@...r.kernel.org>, linux-ext4@...r.kernel.org,
	sfr@...b.auug.org.au, Arnd Bergmann <arnd@...db.de>,
	Avinash Kurup <kurup.avinash@...il.com>
Subject: Re: [next-20101038] Call trace in ext4

On Thu, Oct 28, 2010 at 11:02:14PM +0200, Sedat Dilek wrote:
> 
> I could copy a complete linux-2.6 GIT tree within my $HOME/src, looks good.

Excellent; and attempts to do this before resulted on the BUG_ON
tripping?  If so, that's certainly a good sign!

> 
> Any other test-case you can suggest to be sure things work as expected, now?

Well, given that I haven't been able to replicate myself, no, not
really.

I am curious about your setup.  How much memory do you have on your
system, and how much free memory did you have before running the copy?
(i.e, what does the "free" command display)?

> BTW, feel free to add:
> 
>       Reported-andtested-by: Sedat Dilek <sedat.dilek@...il.com>

I'll certainly give you credit (as well as to the other people who
reported the problem).

Thanks again!!

						- 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