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: <alpine.DEB.2.02.1403111654340.18573@ionos.tec.linutronix.de>
Date:	Tue, 11 Mar 2014 17:02:04 +0100 (CET)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Paul Bolle <pebolle@...cali.nl>
cc:	"H. Peter Anvin" <hpa@...or.com>,
	Jerome Oufella <jerome.oufella@...oirfairelinux.com>,
	Julian Wollrath <jwollrath@....de>, x86@...nel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [RESEND] Fast TSC calibration fails with v3.14-rc1 and later

On Tue, 11 Mar 2014, Paul Bolle wrote:
> On Mon, 2014-03-10 at 21:50 +0100, Thomas Gleixner wrote:
> > Dammit no. We want to know WHY!
> 
> Here I am one and half year after reporting seeing this error. I'm not
> aware of anyone reporting it before me. Anyhow, I don't think things
> were working fine up to v3.13. And in my report (I'm not going to link

You can think what you want. 

According to Julian things were working fine for him and he actually
sat down and found out WHY things stopped working. That's what counts.

I really have a hard time to understand why you are wasting everyones
time with a completely pointless discussion about the printk level of
this particular thing. It's not spewing a backtrace. It's one line of
printk and there is no rule, that recoverable issues are not allowed
to be printed at KERN_ERR level. 

Julian noticed a change of behaviour due to that after 3.13. That's
way more important than your personal dislike of a particular error
level.

Thanks,

	tglx

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