[OpenAFS] OpenAFS on Linux 2.5.x

Derrick J Brashear shadow@dementia.org
Wed, 16 Apr 2003 09:24:13 -0400 (EDT)


On Wed, 16 Apr 2003, chas williams wrote:

> In message <Pine.LNX.4.53.0304160900430.26304@scully.trafford.dementia.org>,Der
> rick J Brashear writes:
> >i know we talked about it here before. making all of the entry points for
> >daemons being kernel threads means we could reduce startup entry to an
> >ioctl done on a file in /proc, or somesuch. then the afsdb handler also
>
> i was actually thinking about something that might be easier like making
> pioctl() an ioctl() on /afs.  i believe you could intercept this easily
> enough at the filesystem.  i dont remember how everything works but
> for pioctl() operations on file it would make sense.  for other operations
> like setpag you might need to open /afs as a dummy fd.

but you still need a way to start the client.

> >tampering with task_struct in addition to being ugly seems not likely to
> >win us any friends, but more importantly, perhaps (or perhaps not) it
> >seems not useful: there appear to be no fields not used that we can
> >piggyback on.
>
> well it would allow you to keep the same scheme, tacking it onto the end
> of the groups field.

setgroups will flush it

> ask to get a field added to task struct to hold our stuff.

i did. i'll try to find out what happened with it.