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: <20171222205109.fjlmvwwmpqgzuqw7@hirez.programming.kicks-ass.net>
Date:   Fri, 22 Dec 2017 21:51:09 +0100
From:   Peter Zijlstra <peterz@...radead.org>
To:     gaurav jindal <gauravjindal1104@...il.com>
Cc:     mingo@...hat.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH]locking:mutex Print warning if trylock in irq context

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.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ