From: Ryan Mallon <rmallon@gmail.com>
To: Sanjeev Sharma <sanjeev_sharma@mentor.com>,
cpw@sgi.com, robinmholt@gmail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sgi-xp: Do not use BUG_ON(!spin_is_locked())
Date: Wed, 20 Aug 2014 09:04:19 +1000 [thread overview]
Message-ID: <53F3D7F3.3080900@gmail.com> (raw)
In-Reply-To: <1407828913-7461-1-git-send-email-sanjeev_sharma@mentor.com>
On 12/08/14 17:35, Sanjeev Sharma wrote:
> on some architecture spin_is_locked() always return false in
> uniprocessor configuration and can therefore not be used
> with BUG_ON.it would be advise to replace with
> lockdep_assert_held().
>
> Signed-off-by: Sanjeev Sharma <Sanjeev_Sharma@mentor.com>
> ---
> drivers/misc/sgi-xp/xpc_channel.c | 6 +++---
> drivers/misc/sgi-xp/xpc_sn2.c | 2 +-
> drivers/misc/sgi-xp/xpc_uv.c | 2 +-
> 3 files changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/misc/sgi-xp/xpc_channel.c b/drivers/misc/sgi-xp/xpc_channel.c
> index 128d561..240fe5a 100644
> --- a/drivers/misc/sgi-xp/xpc_channel.c
> +++ b/drivers/misc/sgi-xp/xpc_channel.c
> @@ -28,7 +28,7 @@ xpc_process_connect(struct xpc_channel *ch, unsigned long *irq_flags)
> {
> enum xp_retval ret;
>
> - DBUG_ON(!spin_is_locked(&ch->lock));
> + lockdep_assert_held(!spin_is_locked(&ch->lock));
This is incorrect, and will break the build with CONFIG_LOCKDEP enabled.
You actually want:
lockdep_assert_held(&ch->lock);
Same for the other instances.
~Ryan
next prev parent reply other threads:[~2014-08-19 23:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 7:35 [PATCH] sgi-xp: Do not use BUG_ON(!spin_is_locked()) Sanjeev Sharma
2014-08-12 18:21 ` Robin Holt
2014-08-19 6:37 ` Sharma, Sanjeev
2014-08-19 23:04 ` Ryan Mallon [this message]
2014-08-20 5:24 ` Sharma, Sanjeev
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=53F3D7F3.3080900@gmail.com \
--to=rmallon@gmail.com \
--cc=cpw@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robinmholt@gmail.com \
--cc=sanjeev_sharma@mentor.com \
/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;
as well as URLs for NNTP newsgroup(s).