The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Brad Chapman <kakadu_croc@yahoo.com>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: brlock_is_locked()?
Date: Wed, 22 Aug 2001 11:33:12 -0700 (PDT)	[thread overview]
Message-ID: <20010822183312.11829.qmail@web10908.mail.yahoo.com> (raw)
In-Reply-To: <20010822.112619.62651200.davem@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 2215 bytes --]

--- "David S. Miller" <davem@redhat.com> wrote:
>    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

Mr. Miller,

	It almost isn't. The problem starts when a third-party protocol
module grabs BR_NETPROTO_LOCK, unloads itself from the networking stack,
and then tries to call ip6_conntrack_protocol_unregister(). Deadlock.
The problem is that we need TWO locks: the brlock to seal the network stack,
and the conntrack rwlock to delete the protocol struct. Sure, you can
always share the rwlock and leave it at that, but if all you need it for
is to load/unload your protocol functions, then why bother polluting
the symbol tables?
	What do you think? Share the rwlock and make everybody who has
the brlock just use the core function?

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/

  reply	other threads:[~2001-08-22 18:33 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         ` brlock_is_locked()? David S. Miller
2001-08-22 18:33           ` Brad Chapman [this message]
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=20010822183312.11829.qmail@web10908.mail.yahoo.com \
    --to=kakadu_croc@yahoo.com \
    --cc=davem@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