Justin, > Tags: upstream
Any time you open a report like this you better make sure that whatever you say holds against the latest upstream release. > It seems that the clone manpage is out of sync with the libc/kernel > reality. > > In particular, the following succeeds, The preceding is nearly meaningless, because so vague. Succeeds where? What kernel? > but the annotation says that it > should not: > > CLONE_NEWNS|CLONE_FS > CLONE_THREAD (because CLONE_SIGHAND is not set) > CLONE_SIGHAND (because CLONE_VM is not set) And how did you test or verify this? If it was with a program, show me the complete clone() call. (By the way, my reading of the 2.6.17-rc2 source says you are wrong on all three counts above, and the man page is right, but I have not run any of my test programs to re-verify that understanding.) > There is also mention of a "CLONE_DETACHED" flag which is not > otherwise mentioned; (the header files indicate that it is ignored). Mention where? Please be precise. > Also, I can't follow the description of sys_clone, mostly because the > prototype doesn't make sense. Instead of being a prototype of clone, > it looks like it is just copied from the definition (somewhere). > Doesn't it make more sense to include something like: > > clone(int flags, void *child_stack, int *parent_tidptr, > struct user_desc *newtls, int *child_tidptr); No, because it is not prototyped in header files. Thus either _syscall5() or syscall() is required. > Instead of the stuff that some scary-looking macro in a burried header > file that generates the definition? :) The people who find it scary probably don't need clone(). Justin -- vague bug reports like this waste my time. (I may be wrong, but this bug report sounds "speculative" -- that is, you don't really have much experience with clone().) Please be _much_ more precise in future reports. Cheers, Michael -- Michael Kerrisk maintainer of Linux man pages Sections 2, 3, 4, 5, and 7 Want to help with man page maintenance? Grab the latest tarball at ftp://ftp.win.tue.nl/pub/linux-local/manpages/, read the HOWTOHELP file and grep the source files for 'FIXME'. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
