linux-kernel - Re: [fix] Too async libata breakage

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: <496722AB.7050805@kernel.org>
Date:	Fri, 09 Jan 2009 19:10:51 +0900
From:	Tejun Heo <tj@...nel.org>
To:	"Justin P. Mattock" <justinmattock@...il.com>
CC:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Jeff Garzik <jgarzik@...hat.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [fix] Too async libata breakage

Hello,

Justin P. Mattock wrote:
> Linus Torvalds wrote:
>> On Thu, 8 Jan 2009, Justin P. Mattock wrote:
>>  
>>> O.K. attached is the results of
>>> dmesg after doing a git-pull
>>> (system didn't freeze, but there's
>>> a slew of warnings); i.g.
>>>     
>>
>> That's a different thing now - some very annoying warnings indeed.
>>
>> Tejun, I think it's yours. And I think it should be removed, or at the
>> very least changed into a WARN_ON_ONCE. Because spamming the console
>> with this is not a good idea:

Yeah, that's WARN_ON() on a pretty hot path.  I'll submit a patch to
convert it to WARN_ON_ONCE() but that's a condition which shouldn't
happen in the first place.  Strange.

Justin, can you please post the output of "lspci -nn" and full kernel
boot log?

Thanks.

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