linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Sven Schnelle <svens@stackframe.org>
Cc: dhowells@redhat.com, linux-fsdevel@vger.kernel.org
Subject: Re: [AFS] prevent double cell registration
Date: Tue, 01 Apr 2008 22:34:01 +0100	[thread overview]
Message-ID: <26826.1207085641@redhat.com> (raw)
In-Reply-To: <87ve31fgpx.fsf@apollo.bitebene.org>

Sven Schnelle <svens@stackframe.org> wrote:

> Just digged again into afs, and stumbled upon this return. I think there
> should be some up_write(&afs_cells_sem); before the return, or am i on the
> wrong track?

Unfortunately not:-(

David

  parent reply	other threads:[~2008-04-01 21:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-21 22:39 [AFS] prevent double cell registration Sven Schnelle
2008-03-25 17:23 ` David Howells
2008-03-25 17:27   ` Sven Schnelle
2008-03-25 19:05   ` David Howells
2008-04-01 20:44     ` Sven Schnelle
2008-04-01 21:34     ` David Howells [this message]
2008-04-02  5:50       ` [PATCH] [PATCH] afs: add missing up_write() on return Sven Schnelle

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=26826.1207085641@redhat.com \
    --to=dhowells@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=svens@stackframe.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).