linux-kernel - Re: Bug: get EXT3-fs error Allocating block in system zone

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, 6 Dec 2007 16:42:19 -0800 (PST)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
cc:	Marco Gatti <marco@...noinflames.de>, linux-kernel@...r.kernel.org,
	Greg KH <greg@...ah.com>, Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: Bug: get EXT3-fs error Allocating block in system zone

On Thu, 6 Dec 2007, Andrew Morton wrote:
> 
> http://bugs.gentoo.org/attachment.cgi?id=135761&action=view
> 
> It disables PCI BARs during sizing.  ISTR Linus opining that this was the
> wrong thing to do?

It looks ok now that it doesn't do it for host controllers. I guess we 
could just apply it.

> ISTR him having opinions on mmconfig too ;)

That piece of unbelievable crap? Have I ever said anything negative about 
something that shitty? I can't imagine having ever badmouthed such a 
mindless and totally broken piece of sh*t hardware/firmware interface.

> We should not require people to use obscure boot options to get their
> machines working.

Arjan swears he'll have a patch for me to only use mmconfig when actually 
appropriate by 2.6.25. In the meantime, the BAR disable is probably worth 
trying.

But the disk errors are something else, doesn't ring a bell. Sounds like 
IO corruption on the group descriptor block or something like that. Might 
be worth testing to see if the problem goes away with less than 4GB of 
RAM..

		Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/