source: branches/3.2/mindi-busybox/docs/nofork_noexec.txt @ 3232

Last change on this file since 3232 was 3232, checked in by bruno, 5 years ago
  • Update mindi-busybox to 1.21.1
  • Property svn:eol-style set to native
File size: 4.0 KB
1    NOEXEC and NOFORK applets.
3Unix shells traditionally execute some commands internally in the attempt
4to dramatically speed up execution. It will be slow as hell if for every
5"echo blah" shell will fork and exec /bin/echo. To this end, shells
6have to _reimplement_ these commands internally.
8Busybox is unique in this regard because it already is a collection
9of reimplemented Unix commands, and we can do the same trick
10for speeding up busybox shells, and more. NOEXEC and NOFORK applets
11are exactly those applets which are eligible for these tricks.
13Applet will be subject to NOFORK/NOEXEC tricks if it is marked as such
14in applets.h. FEATURE_PREFER_APPLETS is a config option which
15globally enables usage of NOFORK/NOEXEC tricks.
16If it is enabled, FEATURE_SH_STANDALONE can be enabled too,
17and then shells will use NOFORK/NOEXEC tricks for ordinary commands.
18NB: shell builtins use these tricks regardless of FEATURE_SH_STANDALONE
21In C, if you want to call a program and wait for it, use
22spawn_and_wait(argv), BB_EXECVP(prog,argv) or BB_EXECLP(prog,argv0,...).
23They check whether program name is an applet name and optionally
24do NOFORK/NOEXEC thing depending on configuration.
27    NOEXEC
29NOEXEC applet should work correctly if another applet forks and then
30executes exit(<applet>_main(argc,argv)) in the child. The rules
31roughly are:
33* do not expect shared global variables/buffers to be in their
34  "initialized" state. Examples: xfunc_error_retval can be != 1,
35  bb_common_bufsiz1 can be scribbled over, ...
36* do not expect that stdio wasn't used before. Calling set[v]buf()
37  can be disastrous.
38* ...
40NOEXEC applets save only one half of fork+exec overhead.
41NOEXEC trick is disabled for NOMMU build.
44    NOFORK
46NOFORK applet should work correctly if another applet simply runs
47<applet>_main(argc,argv) and then continues with its business.
48xargs, find, shells do it (grep for "spawn_and_wait" and
49"run_nofork_applet" to find more users).
51This poses much more serious limitations on what applet can do:
53* all NOEXEC limitations apply.
54* do not ever exit() or exec().
55  - xfuncs are okay. They are using special trick to return
56    to the caller applet instead of dying when they detect "x" condition.
57  - you may "exit" to caller applet by calling xfunc_die(). Return value
58    is taken from xfunc_error_retval.
59  - fflush_stdout_and_exit(n) is ok to use.
60* do not use shared global data, or save/restore shared global data
61  (e.g. bb_common_bufsiz1) prior to returning.
62  - getopt32() is ok to use. You do not need to save/restore option_mask32,
63    it is already done by core code.
64* if you allocate memory, you can use xmalloc() only on the very first
65  allocation. All other allocations should use malloc[_or_warn]().
66  After first allocation, you cannot use any xfuncs.
67  Otherwise, failing xfunc will return to caller applet
68  without freeing malloced data!
69* All allocated data, opened files, signal handlers, termios settings,
70  O_NONBLOCK flags etc should be freed/closed/restored prior to return.
71* ...
73NOFORK applets give the most of speed advantage, but are trickiest
74to implement. In order to minimize amount of bugs and maintenance,
75prime candidates for NOFORK-ification are those applets which
76are small and easy to audit, and those which are more likely to be
77frequently executed from shell/find/xargs, particularly in shell
78script loops. Applets which mess with signal handlers, termios etc
79are probably not worth the effort.
81Any NOFORK applet is also a NOEXEC applet.
84    Relevant CONFIG options
87  BB_EXECVP(cmd, argv) will try to exec /proc/self/exe
88    if command's name matches some applet name
89  applet tables will contain NOFORK/NOEXEC bits
90  spawn_and_wait(argv) will do NOFORK/NOEXEC tricks
93  shells will try to exec /proc/self/exe if command's name matches
94    some applet name
95  shells will do NOEXEC trick on NOEXEC applets
98  shells will do NOFORK trick on NOFORK applets
Note: See TracBrowser for help on using the repository browser.