From: Brad Chapman <kakadu_croc@yahoo.com>
To: Ben LaHaise <bcrl@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: brlock_is_locked()?
Date: Wed, 22 Aug 2001 11:00:56 -0700 (PDT) [thread overview]
Message-ID: <20010822180056.58350.qmail@web10902.mail.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0108221231260.19638-100000@touchme.toronto.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1201 bytes --]
--- Ben LaHaise <bcrl@redhat.com> wrote:
> On Wed, 22 Aug 2001, Brad Chapman wrote:
>
> > restart:
> > if (brlock_is_locked(BR_NETPROTO_LOCK)) {
> > CRITICAL_SECTION
> > br_write_unlock_bh(BR_NETPROTO_LOCK);
> > }
> > else {
> > /* Let's get dizzy */
> > br_write_lock_bh(BR_NETPROTO_LOCK);
> > goto restart;
> > }
>
> That code can never work. None of the linux spinlocks track ownership, so
> checking if a lock is locked tells you if your process or another has
> ownership of the lock. The above pseudo code is going to result in lots
> of mangled data.
>
> -ben
>
Mr. LaHaise,
Eeek! Sorry. What do you expect at 10:00 at night? ;-)
I'm not talking about _who_ owns the lock, I'm talking about whether
the lock itself is locked. I don't care which process is using the lock;
I just want to know if _somebody_ is using it. Is this possible?
Brad
=====
Brad Chapman
Permanent e-mail: kakadu_croc@yahoo.com
Current e-mail: kakadu@adelphia.net
Reply to the address I used in the message to you,
please!
__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/
next prev parent reply other threads:[~2001-08-22 18:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-22 13:04 brlock_is_locked()? Brad Chapman
2001-08-22 16:33 ` brlock_is_locked()? Ben LaHaise
2001-08-22 18:00 ` Brad Chapman [this message]
2001-08-22 18:03 ` brlock_is_locked()? David S. Miller
2001-08-22 18:17 ` brlock_is_locked()? Brad Chapman
2001-08-22 18:26 ` brlock_is_locked()? David S. Miller
2001-08-22 18:33 ` brlock_is_locked()? Brad Chapman
2001-08-22 18:47 ` brlock_is_locked()? David S. Miller
2001-08-22 18:53 ` brlock_is_locked()? Brad Chapman
2001-08-22 19:00 ` brlock_is_locked()? David S. Miller
2001-08-22 19:08 ` brlock_is_locked()? Brad Chapman
2001-08-24 6:49 ` brlock_is_locked()? Jens Axboe
2001-08-24 14:11 ` brlock_is_locked()? Brad Chapman
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=20010822180056.58350.qmail@web10902.mail.yahoo.com \
--to=kakadu_croc@yahoo.com \
--cc=bcrl@redhat.com \
--cc=linux-kernel@vger.kernel.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®