From: gaurav jindal <gauravjindal1104@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH]locking:mutex Print warning if trylock in irq context
Date: Sat, 23 Dec 2017 02:38:48 +0530 [thread overview]
Message-ID: <20171222210848.GA12389@gaurav.jindal> (raw)
In-Reply-To: <20171222205109.fjlmvwwmpqgzuqw7@hirez.programming.kicks-ass.net>
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.
prev parent reply other threads:[~2017-12-22 21:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-22 20:45 [PATCH]locking:mutex Print warning if trylock in irq context gaurav jindal
2017-12-22 20:51 ` Peter Zijlstra
2017-12-22 21:08 ` gaurav jindal [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171222210848.GA12389@gaurav.jindal \
--to=gauravjindal1104@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.