linux-kernel - Re: mmiotracer hangs the system

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: <CAHp75VcLh4j6rpRcWg8SPaS2Nnvh_wUiMh9FqqfYHY6K2R6qSA@mail.gmail.com>
Date:	Tue, 2 Aug 2016 19:08:24 +0300
From:	Andy Shevchenko <andy.shevchenko@...il.com>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Karol Herbst <karolherbst@...il.com>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Ingo Molnar <mingo@...nel.org>
Subject: Re: mmiotracer hangs the system

On Tue, Aug 2, 2016 at 6:31 PM, Steven Rostedt <rostedt@...dmis.org> wrote:
> On Tue, 2 Aug 2016 18:07:38 +0300
> Andy Shevchenko <andy.shevchenko@...il.com> wrote:
>
>> Use another Karol's address (found in MAINTAINERS)
>>
>> On Tue, Aug 2, 2016 at 6:05 PM, Andy Shevchenko
>> <andy.shevchenko@...il.com> wrote:
>> > +Cc: Karol, Ingo
>> >
>> > On Tue, Aug 2, 2016 at 1:08 PM, Andy Shevchenko
>> > <andy.shevchenko@...il.com> wrote:
>> >> Hi!
>> >>
>> >> I'm trying to use mmio tracer with recent kernels (in this particular
>> >> case today's linux-next).
>> >
>> > Tested on other board and found that v4.5 works while v4.5.7 doesn't.
>> > Bisecting to
>> >
>> > commit d62a28a60562a8ba82e67e13c268245f37e796cb
>> > Author: Karol Herbst <nouveau@...olherbst.de>
>> > Date:   Thu Mar 3 02:03:11 2016 +0100
>> >
>> >     x86/mm/kmmio: Fix mmiotrace for hugepages
>> >
>> >     commit cfa52c0cfa4d727aa3e457bf29aeff296c528a08 upstream.
>> >
>> > Reverting _helps_ for x86 and x86_64 builds.
>> >
>
> That commit was added in 4.6. Does that kernel work? Maybe it was a bad
> backport?

I don't think so, since linux-next doesn't work until I revert this commit.

I can try exactly v4.6 (yep, I tried stable versions, including
v4.4.16 that's why all of them failed to me) if you still would like
me to do so.


-- 
With Best Regards,
Andy Shevchenko