linux-kernel - Re: [PATCH] perf/core: fix a possible deadlock scenario

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 19 Jul 2018 15:28:34 +0200
From:   Jiri Olsa <jolsa@...hat.com>
To:     Cong Wang <xiyou.wangcong@...il.com>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        Peter Zijlstra <peterz@...radead.org>,
        Ingo Molnar <mingo@...hat.com>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Arnaldo Carvalho de Melo <acme@...nel.org>,
        Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
        Namhyung Kim <namhyung@...nel.org>,
        stable <stable@...r.kernel.org>
Subject: Re: [PATCH] perf/core: fix a possible deadlock scenario

On Wed, Jul 18, 2018 at 01:21:11PM -0700, Cong Wang wrote:

SNIP

> > hum, the swevent pmu does not triger NMI, so that timer
> > will never be touched in NMI context
> 
> Good to know! So I worry too much here.
> 
> But still, given hrtimer interrupt is called with IRQ disabled, getting
> stuck in a hrtimer callback could also block IPI handler, therefore
> causing soft lockups.
> 
> Let me know if you want me to adjust the changelog for this.

yep, it's confusing, I think it should be removed from changelog

jirka