mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: "David S. Miller" <davem@davemloft.net>
Cc: tedu@coverity.com, linux-kernel@vger.kernel.org, ralf@linux-mips.org
Subject: Re: some missing spin_unlocks
Date: Tue, 23 Aug 2005 18:54:03 +0200	[thread overview]
Message-ID: <1124816044.3218.18.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20050823.094603.29591786.davem@davemloft.net>


> This one needs more care.  We can't drop the lock, because
> the destroy actions need to be protected by that lock, but
> we can't release the lock after rose_destroy_socket() because
> the object may not even exist any longer.


does it matter? can ANYTHING be spinning on the lock? if not .. can we
just let the lock go poof and not unlock it... 


  reply	other threads:[~2005-08-23 16:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-22 22:26 Ted Unangst
2005-08-23 16:46 ` David S. Miller
2005-08-23 16:54   ` Arjan van de Ven [this message]
2005-08-23 17:30     ` David S. Miller
2005-08-23 17:40       ` Arjan van de Ven
2005-08-23 17:46         ` David S. Miller
2005-08-24 15:56 ` Lee Revell
2005-08-24 17:01   ` Takashi Iwai

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=1124816044.3218.18.camel@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ralf@linux-mips.org \
    --cc=tedu@coverity.com \
    /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®