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: <20091012101746.GC15777@elte.hu>
Date:	Mon, 12 Oct 2009 12:17:46 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	"Justin P. Mattock" <justinmattock@...il.com>
Cc:	rostedt@...dmis.org, Jason Baron <jbaron@...hat.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Li Zefan <lizf@...fujitsu.com>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: system gets stuck in a lock during boot


* Justin P. Mattock <justinmattock@...il.com> wrote:

> Steven Rostedt wrote:
>> On Wed, 2009-10-07 at 11:45 -0700, Justin P. Mattock wrote:
>>
>>    
>>>>
>>>>        
>>> yep like I said I owe you guys an apology, for
>>> my mistake(thanks for taking the time).
>>>      
>>
>> Well, thank you for reporting it. If nobody reports any problems, we
>> just assume everything is OK, and as people curse us out and look for
>> alternatives, we will be sipping our mai-tais in ignorant bliss.
>>
>> -- Steve
>>
>>    
>
> agree, my main concern when reporting is to make sure that it's a real 
> issue, and not a mistake like this one.

Well, it can be really hard to filter out whether a problem is somehow 
self-inflicted or caused by the kernel proper - thus we generally prefer 
over-reporting over under-reporting.

Even if it's self-inflicted it's useful on a meta level: if many people 
report it then we might end up adding more safety guards to disable a 
particular common pattern of shoot-foot-self incidents.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ