linux-kernel - Re: perf samples too long without perf running (?!?)

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] [day] [month] [year] [list]

Message-ID: <1394298766.2741.7.camel@x220>
Date:	Sat, 08 Mar 2014 18:12:46 +0100
From:	Paul Bolle <pebolle@...cali.nl>
To:	Andy Lutomirski <luto@...capital.net>
Cc:	Markus Trippelsdorf <markus@...ppelsdorf.de>,
	Mike Galbraith <umgwanakikbuti@...il.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: perf samples too long without perf running (?!?)

On Sat, 2014-03-08 at 08:22 -0800, Andy Lutomirski wrote:
> Is it just me or is this whole situation screwed up for multiple reasons?

One minor reason would be that this message should read (say) 
    perf samples taking too long (2503 ns > 2500 ns), [...]

At least, that's what I thought after diving into the code to see what
was causing warnings like these.

And, since apparently things are just fine without administrator
intervention, I'd say another minor reason is that printing this at
KERN_INFO or KERN_NOTICE level should be enough here.


Paul Bolle

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