From: "David S. Miller" <davem@davemloft.net>
To: kaber@trash.net
Cc: daniele@orlandi.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: proto_unregister sleeps while atomic
Date: Tue, 06 Sep 2005 16:07:28 -0700 (PDT) [thread overview]
Message-ID: <20050906.160728.25203864.davem@davemloft.net> (raw)
In-Reply-To: <431E1FE9.7030405@trash.net>
From: Patrick McHardy <kaber@trash.net>
Date: Wed, 07 Sep 2005 01:02:01 +0200
> You're right, good catch. This patch fixes it by moving the lock
> down to the list-operation which it is supposed to protect.
I think we need to unlink from the list first if you're
going to do it this way. Otherwise someone can find the
protocol via lookup, and then bogusly try to use the SLAB
cache we're freeing up.
Or does something else prevent this?
next prev parent reply other threads:[~2005-09-06 23:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200509070026.34999.daniele@orlandi.com>
2005-09-06 23:02 ` proto_unregister sleeps while atomic Patrick McHardy
2005-09-06 23:07 ` David S. Miller [this message]
2005-09-06 23:42 ` Patrick McHardy
2005-09-07 2:48 ` David S. Miller
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=20050906.160728.25203864.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=daniele@orlandi.com \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).