From: "David S. Miller" <davem@redhat.com>
To: Stefan Rompf <srompf@isg.de>
Cc: mostrows@watson.ibm.com, netdev@oss.sgi.com
Subject: Re: Deadlock in sungem/ip_auto_config/linkwatch
Date: Mon, 5 Jan 2004 11:02:48 -0800 [thread overview]
Message-ID: <20040105110248.04ed06b7.davem@redhat.com> (raw)
In-Reply-To: <200401051550.51063.srompf@isg.de>
On Mon, 5 Jan 2004 15:50:50 +0100
Stefan Rompf <srompf@isg.de> wrote:
> Btw, what is the planned difference between rtnl_shlock() and rtnl_exlock()?
> Even though the later is a null operation right now, I don't want to hold
> more locks than needed in the linkwatch code.
The idea was originally to make the RTNL semaphore a read-write one,
but I doubt we'll ever make that happen and the shlock bits will just
disappear entirely.
prev parent reply other threads:[~2004-01-05 19:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-05 13:07 Deadlock in sungem/ip_auto_config/linkwatch Michal Ostrowski
2004-01-05 14:50 ` Stefan Rompf
2004-01-05 16:19 ` Michal Ostrowski
2004-01-05 16:50 ` Stefan Rompf
2004-01-05 19:02 ` David S. Miller [this message]
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=20040105110248.04ed06b7.davem@redhat.com \
--to=davem@redhat.com \
--cc=mostrows@watson.ibm.com \
--cc=netdev@oss.sgi.com \
--cc=srompf@isg.de \
/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).