In message <[EMAIL PROTECTED]>, Robe rt Watson writes: >On Fri, 11 May 2001, Poul-Henning Kamp wrote: > >> In message <[EMAIL PROTECTED]>, Bruce Evan >> s writes: >> >> >> Blame the poor design of mount(2) (and ask Adrian when he fixes >> >> it :-) >> > >> >It must be the excellent design of mount(2) that makes it so easy to >> >do things with it where it can be used :-). >> >> Just too bad it wasn't designed so that it can be used from kernel >> processes as well :-( > >I've made this observation before, of course, but it is my general >opionion that, leaving aside uio structures, awareness of "userland" data >pointers should generall be limited to the system call code rather than >the service implementation. The existence of userland points in VFS calls >(and I've introduced one myself in the vfs_extattrctl call) is generally >evil. It makes it much harder to initiate a service from within a kernel >thread or process, and do ABI wrapping. Well, if I'm not allowed to gripe about that (although in reality you agree with me :-) then I'll gripe about the "max 32 mount options" limitation. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
