From: "David S. Miller" <davem@redhat.com>
To: kakadu_croc@yahoo.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: brlock_is_locked()?
Date: Wed, 22 Aug 2001 11:26:19 -0700 (PDT) [thread overview]
Message-ID: <20010822.112619.62651200.davem@redhat.com> (raw)
In-Reply-To: <20010822181755.39925.qmail@web10905.mail.yahoo.com>
In-Reply-To: <20010822.110316.57459277.davem@redhat.com> <20010822181755.39925.qmail@web10905.mail.yahoo.com>
From: Brad Chapman <kakadu_croc@yahoo.com>
Date: Wed, 22 Aug 2001 11:17:55 -0700 (PDT)
At this section of the code, it doesn't really matter who in the
netfilter/network stack has BR_NETPROTO_LOCK, just that we need to know if
it's already locked by someone else, or unlocked for us to use. Is what I'm
asking for physically possible?
As a reader, the BR_NETPROTO_LOCK nests. So no deadlock.
If the situation involves a writer, you must make sure that locking
rules are well defined and abided by. No matter what you do, if you
try to conditionalize locking by testing if the lock is held, another
SMP can always get in there after you check it and corrupt your data.
The lock is basically pointless if you start testing it's locked
state.
Basically, "fix your code" ;-)
It's often easy to do this. If you have two paths, one which is going
to already have the lock and one which won't, just make two functions
like so:
void __func(void)
{
do_stuff();
}
void func(void)
{
lock();
__func();
unlock();
}
I don't see why this is such a big problem.
Later,
David S. Miller
davem@redhat.com
next prev parent reply other threads:[~2001-08-22 18:26 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 ` brlock_is_locked()? Brad Chapman
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 ` David S. Miller [this message]
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=20010822.112619.62651200.davem@redhat.com \
--to=davem@redhat.com \
--cc=kakadu_croc@yahoo.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