All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Schnelle <svens@stackframe.org>
To: dhowells@redhat.com
Cc: linux-fsdevel@vger.kernel.org
Subject: [AFS] prevent double cell registration
Date: Fri, 21 Mar 2008 23:39:30 +0100	[thread overview]
Message-ID: <868x0bog65.fsf@deprecated.bitebene.org> (raw)

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


kafs doesn't check if the cell already exists - so if you do an
echo "add newcell.org 1.2.3.4" >/proc/fs/afs/cells it will try to
create this cell again. kobject will also complain about a double
registration. To prevent such problems, return -EEXIST in that case.
---
 fs/afs/cell.c |    9 +++++++++
 1 files changed, 9 insertions(+), 0 deletions(-)

diff --git a/fs/afs/cell.c b/fs/afs/cell.c
index 970d38f..87934b3 100644
--- a/fs/afs/cell.c
+++ b/fs/afs/cell.c
@@ -127,6 +127,15 @@ struct afs_cell *afs_cell_create(const char *name, char *vllist)
 
 	_enter("%s,%s", name, vllist);
 
+	read_lock(&afs_cells_lock);
+	list_for_each_entry(cell, &afs_cells, link) {
+		if(!strcasecmp(cell->name, name)) {
+			read_unlock(&afs_cells_lock);
+			return ERR_PTR(-EEXIST);
+		}
+	}
+	read_unlock(&afs_cells_lock);
+
 	cell = afs_cell_alloc(name, vllist);
 	if (IS_ERR(cell)) {
 		_leave(" = %ld", PTR_ERR(cell));
-- 
1.5.4.3


[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]

             reply	other threads:[~2008-03-21 23:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-21 22:39 Sven Schnelle [this message]
2008-03-25 17:23 ` [AFS] prevent double cell registration 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
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=868x0bog65.fsf@deprecated.bitebene.org \
    --to=svens@stackframe.org \
    --cc=dhowells@redhat.com \
    --cc=linux-fsdevel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.