linux-kernel - Re: [PATCH v3] Added perf functionality to mmdc driver

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: <20160831102937.GC4783@leverpostej>
Date:   Wed, 31 Aug 2016 11:30:36 +0100
From:   Mark Rutland <mark.rutland@....com>
To:     Zhengyu Shen <zhengyu.shen@....com>
Cc:     Shawn Guo <shawnguo@...nel.org>, Zhi Li <lznuaa@...il.com>,
        Frank Li <frank.li@....com>,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>,
        kernel list <linux-kernel@...r.kernel.org>,
        "peterz@...radead.org" <peterz@...radead.org>,
        "mingo@...hat.com" <mingo@...hat.com>,
        "acme@...nel.org" <acme@...nel.org>,
        "alexander.shishkin@...ux.intel.com" 
        <alexander.shishkin@...ux.intel.com>
Subject: Re: [PATCH v3] Added perf functionality to mmdc driver

On Tue, Aug 30, 2016 at 08:01:18PM +0000, Zhengyu Shen wrote:
> Hi, I've done some testing with the fuzzer.

Great! Many thanks for doing this.

> Mmdc was only responsible for one crash which I fixed (had to remove
> the event from the pmu properly). 

Ok. I take it that there will be a v4 appearing shortly with that fix?

> Other drivers also cause crashes and the program reports that events are
> Throttling. Is this normal?

Throttling is normal, and warnings about throttling can (generally) be
safely ignored.

Crashes are very bad. Do you have any logs from those crashes in other
drivers that you can share?

It is possible that a bug in one driver causes failures in another (e.g.
if events are erroneously grouped together), so it's not alwyas clear if
this is an unrelated bug (though if you can trigger the issue without
your driver present, it clearly is).

Thanks,
Mark.