From: Julia Lawall <julia.lawall@lip6.fr>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Joe Perches <joe@perches.com>,
Prakruthi Deepak Heragu <pheragu@codeaurora.org>,
apw@canonical.com, Julia Lawall <julia.lawall@lip6.fr>,
Dan Carpenter <error27@gmail.com>,
linux-kernel@vger.kernel.org, ckadabi@codeaurora.org,
tsoni@codeaurora.org, bryanh@codeaurora.org,
Israel Schlesinger <israels@codeaurora.org>,
Stepan Moskovchenko <stepanm@codeaurora.org>,
baijiaju1990@gmail.com
Subject: Re: [PATCH] checkpatch: Add warnings for use of mdelay()
Date: Fri, 6 Jul 2018 07:49:18 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1807060747280.3506@hadrien> (raw)
In-Reply-To: <20180705081953.pmvpmtzm273eb6yk@mwanda>
On Thu, 5 Jul 2018, Dan Carpenter wrote:
> Neither Smatch nor Coccinelle do a good job tracking when you're in
> atomic context. I've wanted to add this to Smatch but even then it
> would be to warn that "We're holding a spinlock so we can't sleep".
> It's trickier to say for sure when you're not holding a lock...
Jia-Ju Bai is working on this. The tool is available on github. It's
still being improved, though, so perhaps it's not yet ready for eg 0-day
inclusion. He can give more details.
julia
next prev parent reply other threads:[~2018-07-06 6:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 18:18 Prakruthi Deepak Heragu
2018-07-04 18:30 ` Joe Perches
2018-07-05 8:19 ` Dan Carpenter
2018-07-06 5:49 ` Julia Lawall [this message]
2018-07-07 12:09 ` Jia-Ju Bai
-- strict thread matches above, loose matches on Subject: below --
2010-07-27 17:11 Israel Schlesinger
2010-07-27 17:22 ` Joe Perches
2010-07-27 17:31 ` Jonathan Corbet
2010-07-27 17:32 ` Patrick Pannuto
2010-07-27 19:16 ` Andrew Morton
2010-07-28 9:44 ` Andy Whitcroft
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=alpine.DEB.2.20.1807060747280.3506@hadrien \
--to=julia.lawall@lip6.fr \
--cc=apw@canonical.com \
--cc=baijiaju1990@gmail.com \
--cc=bryanh@codeaurora.org \
--cc=ckadabi@codeaurora.org \
--cc=dan.carpenter@oracle.com \
--cc=error27@gmail.com \
--cc=israels@codeaurora.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pheragu@codeaurora.org \
--cc=stepanm@codeaurora.org \
--cc=tsoni@codeaurora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®