Messages in this thread | | | Subject | Re: [PATCH] add a stub by which a module can bind to the AFS syscall | Date | Wed, 30 Apr 2003 11:13:23 -0400 | From | chas williams <> |
| |
In message <20030430160239.A8956@infradead.org>,Christoph Hellwig writes: >We need to repeat a mistake others did has never been a valid >argument in linux devlopment.. Anyway, it's really hard to judge about >this before seeing the actual implementation instead of just saying >here's a stub I need.
at the time afs was written it wasnt a mistake. syscall was the only (easy) way into the kernel from user space. adding multiple syscalls would have just been completely painful. as for examples, pioctl() -- the user space of the afs syscall -- is a bit like syssgi() i am afraid:
venus/fs.c: code = pioctl(0, VIOC_GETCELLSTATUS, &blob, 1); venus/fs.c: code = pioctl(0, VIOC_SETRXKCRYPT, &blob, 1); vlserver/sascnvldb.c: code = pioctl(ti->data, VIOCGETVOLSTAT, &blob, 1); auth/ktc_nt.c: code = pioctl(0, VIOCNEWGETTOK, &iob, 0); auth/ktc_nt.c: code = pioctl(0, VIOCDELTOK, &iob, 0); package/package.c: code = pioctl(0, VIOC_AFS_SYSNAME, &data, 1); venus/up.c: code = pioctl(file1, _VICEIOCTL(2), &blob, 1);
in reality, very few things other than afs are going to want to use the afs syscall (arla might be a possible user). - 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/
| |