linux-kernel - Re: [PATCH]locking:mutex Print warning if trylock in irq context

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: <20171222210848.GA12389@gaurav.jindal>
Date:   Sat, 23 Dec 2017 02:38:48 +0530
From:   gaurav jindal <gauravjindal1104@...il.com>
To:     Peter Zijlstra <peterz@...radead.org>
Cc:     mingo@...hat.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH]locking:mutex Print warning if trylock in irq context

On Fri, Dec 22, 2017 at 09:51:09PM +0100, Peter Zijlstra wrote:
> On Sat, Dec 23, 2017 at 02:15:19AM +0530, gaurav jindal wrote:
> > Since mutex_trylock must not be called from interrupt context, a robustness
> > can be added to this function by throwing a warning if it is called in
> > interrupt context.
> > It would help to make debugging easier in case of undesired calling of this
> > function.
> 
> Or you run with lockdep enabled and not make this thing slower for
> everybody.
Got the point. thanks for making it clear and consideration.