From: David Howells <dhowells@redhat.com>
In-Reply-To: <20040914021206.6879ed86.akpm@osdl.org> 
References: <20040914021206.6879ed86.akpm@osdl.org>  <20040913015003.5406abae.akpm@osdl.org> <200409132306.38340.rjw@sisk.pl> <16710.46269.961782.124751@thebsh.namesys.com> 
To: Andrew Morton <akpm@osdl.org>, jamesm@redhat.com
Cc: Nikita Danilov <nikita@clusterfs.com>, rjw@sisk.pl, ak@suse.de,
       linux-kernel@vger.kernel.org
Subject: Re: 2.6.9-rc1-mm5 
User-Agent: EMH/1.14.1 SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.6 Emacs/21.3 (i386-redhat-linux-gnu) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen")
Content-Type: text/plain; charset=US-ASCII
Date: Tue, 14 Sep 2004 14:21:13 +0100
Message-ID: <13185.1095168073@redhat.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 939
Lines: 28


> >  Correct solution is to put both structs into proper namespaces by
> >  prefixing them.
> 
> struct key was pretty dumb of both of you, but reiserfs was dumb first.

Well, I argue that it wasn't that dumb - in this case it's meant to be a
generic mechanism usable by everything in the kernel or userspace that needs
authentication, authorisation, or crypto tokens. I use EXT3 rather than
ReiserFS, so it didn't become an issue.

> David, what do you want it renamed to?

key_struct? token? key_token?

Possibly ticket or principal, though they make it sound like it's specifically
for Kerberos, so perhaps not.

What I need is a thesaurus.

JamesM: any good suggestion as to a name?

David
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/