Re: [OpenAFS-devel] setgroups() fails to change pag under linux 2.6

[Roland Kuhn]

Hi Chas!

On 9 Aug 2006, at 15:41, chas williams - CONTRACTOR wrote:

In message <[EMAIL PROTECTED]>,Garrett Wollman w

rites:

Doesn't matter, so long as each PAG gets a distinct memory location.
In a real implementation, it would probably be a pointer to a
reference count.

together objects.  there should not be identifier reuse.  pointers to
kernel memory are very likely to be reused (mostly due to the slab
allocator).  since you might pass these identifiers to a user process

might hold onto these things.

negative. it really should just be an indentifier that is used to group you cant let them repeat since you have no idea how long a user process

Ciao,
                    Roland

--
TU Muenchen, Physik-Department E18, James-Franck-Str., 85748 Garching
Telefon 089/289-12575; Telefax 089/289-12570
--
CERN office: 892-1-D23 phone: +41 22 7676540 mobile: +41 76 487 4482
--
Any society that would give up a little liberty to gain a little
security will deserve neither and lose both.  - Benjamin Franklin
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12

PGP++ t+(++) 5 R+ tv-- b+ DI++ e+++>++++ h---- y+++
------END GEEK CODE BLOCK------

You got me curious. I should probably watched this thread more closely and maybe it would then be clear to me: Why should userspace ever see a PAG identifier? What should it be able to do with it? From my (very limited) understanding a PAG should behave essentially like a session: it is inherited by fork()/exec(), you can detach from it, you can create a new one and you can modify it (klog). For none of these operations you need to know how the kernel internally handles this... GS/CS/M/MU d-(++) s:+ a-> C+++ UL++++ P+++ L+++ E(+) W+ !N K- w--- M + !V Y+

PGP.sig
Description: This is a digitally signed message part