mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nikita Danilov <Nikita@Namesys.COM>
To: Joe Thornber <thornber@redhat.com>
Cc: Arjan van de Ven <arjanv@redhat.com>,
	Prashanth T <prasht@in.ibm.com>,
	rml@tech9.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rwlock_is_locked undefined for UP systems
Date: Fri, 16 Jan 2004 18:14:06 +0300	[thread overview]
Message-ID: <16391.65470.831998.936394@laputa.namesys.com> (raw)
In-Reply-To: <20040116145311.GD1740@reti>

Joe Thornber writes:
 > On Fri, Jan 16, 2004 at 02:55:50PM +0100, Arjan van de Ven wrote:
 > > On Fri, 2004-01-16 at 14:45, Prashanth T wrote:
 > > > Hi,
 > > >     I had to use rwlock_is_locked( ) with linux2.6 for kdb and noticed that
 > > > this routine to be undefined for UP.  I have attached the patch for 2.6.1
 > > > below to return 0 for rwlock_is_locked( ) on UP systems.
 > > > Please let me know.
 > > 
 > > I consider any user of this on UP to be broken, just like UP use of
 > > spin_is_locked() is always a bug..... better a compiletime bug than a
 > > runtime bug I guess...
 > 
 > Then maybe a #error explaining this is in order ?

So, if there is a function

void foo_locked(struct bar *obj)
{
    /* check that we are called with obj's lock held */
    BUG_ON(!rwlock_is_locked(&obj->lock));
    /* proceed with obj. */
}

it should now be changed to the

void foo_locked(struct bar *obj)
{
#ifdef CONFIG_SMP
    BUG_ON(!rwlock_is_locked(&obj->lock));
#endif
    /* proceed with obj. */
}

?

 > 
 > - Joe
 > 

Nikita.

 > 

  reply	other threads:[~2004-01-16 15:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-16 13:45 Prashanth T
2004-01-16 13:55 ` Arjan van de Ven
2004-01-16 14:53   ` Joe Thornber
2004-01-16 15:14     ` Nikita Danilov [this message]
2004-01-16 18:10       ` Mike Fedyk
2004-01-16 14:09 ` Christoph Hellwig
2004-01-19  6:12   ` Prashanth T

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=16391.65470.831998.936394@laputa.namesys.com \
    --to=nikita@namesys.com \
    --cc=arjanv@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=prasht@in.ibm.com \
    --cc=rml@tech9.net \
    --cc=thornber@redhat.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

all inboxes | Powered by JetHome®