linux-kernel - Re: [BUG] perf top: --stdio causes continuous refresh

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: <20140211121411.GA4368@infradead.org>
Date:	Tue, 11 Feb 2014 10:14:11 -0200
From:	Arnaldo Carvalho de Melo <acme@...hat.com>
To:	Peter Hurley <peter@...leysoftware.com>
Cc:	David Ahern <dsahern@...il.com>,
	Stephane Eranian <eranian@...gle.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Peter Zijlstra <peterz@...radead.org>,
	"mingo@...e.hu" <mingo@...e.hu>, Jiri Olsa <jolsa@...hat.com>,
	Eric Dumazet <edumazet@...gle.com>
Subject: Re: [BUG] perf top: --stdio causes continuous refresh

Em Mon, Feb 10, 2014 at 09:15:42PM -0500, Peter Hurley escreveu:
> >Bisected it down to:

> >eb3e4668bd9e0bbda592e830e889f137e44ec9e4 is the first bad commit
> >Author: Peter Hurley <peter@...leysoftware.com>
> >Date:   Mon Dec 2 14:24:42 2013 -0500

> >     n_tty: Un-inline slow-path n_tty_receive_char()

> >In a hurry now, will continue later, trying to understand what is the problem
> >introduced by the above cset...

> >Need to revert just this one to confirm that it is the culprit, etc.

> Thanks for the report and bisect. Seems unlikely this commit is the
> cause, but very likely to be some change I made since 3.13, since
> I can repro on 3.14-rc1 but not on 3.13.2 -stable. I can also repro
> this on 3.12 + the patch stack from me for 3.13 and 3.14.

> I'm looking into this now.

I just reverted just this cset and the problem persisted, so I'll wait
for you on this one :-)

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