1 NOEXEC and NOFORK applets.
3 Unix shells traditionally execute some commands internally in the attempt
4 to 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
6 have to _reimplement_ these commands internally.
8 Busybox is unique in this regard because it already is a collection
9 of reimplemented Unix commands, and we can do the same trick
10 for speeding up busybox shells, and more. NOEXEC and NOFORK applets
11 are exactly those applets which are eligible for these tricks.
13 Applet will be subject to NOFORK/NOEXEC tricks if it is marked as such
14 in applets.h. FEATURE_PREFER_APPLETS is a config option which
15 globally enables usage of NOFORK/NOEXEC tricks.
16 If it is enabled, FEATURE_SH_STANDALONE can be enabled too,
17 and then shells will use NOFORK/NOEXEC tricks for ordinary commands.
18 NB: shell builtins use these tricks regardless of FEATURE_SH_STANDALONE
19 or FEATURE_PREFER_APPLETS.
21 In C, if you want to call a program and wait for it, use
22 spawn_and_wait(argv), BB_EXECVP(prog,argv) or BB_EXECLP(prog,argv0,...).
23 They check whether program name is an applet name and optionally
24 do NOFORK/NOEXEC thing depending on configuration.
29 NOEXEC applet should work correctly if another applet forks and then
30 executes exit(<applet>_main(argc,argv)) in the child. The rules
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 (although usually xfunc_error_retval's state is not a problem).
37 * do not expect that stdio wasn't used before. Calling set[v]buf()
41 NOEXEC applets save only one half of fork+exec overhead.
42 NOEXEC trick is disabled for NOMMU build.
47 NOFORK applet should work correctly if another applet simply runs
48 <applet>_main(argc,argv) and then continues with its business.
49 xargs, find, shells do it (grep for "spawn_and_wait" and
50 "run_nofork_applet" to find more users).
52 This poses much more serious limitations on what applet can do:
54 * all NOEXEC limitations apply.
55 * do not ever exit() or exec().
56 - xfuncs are okay. They are using special trick to return
57 to the caller applet instead of dying when they detect "x" condition.
58 - you may "exit" to caller applet by calling xfunc_die(). Return value
59 is taken from xfunc_error_retval.
60 - fflush_stdout_and_exit(n) is ok to use.
61 * do not use shared global data, or save/restore shared global data
62 (e.g. bb_common_bufsiz1) prior to returning.
63 - getopt32() is ok to use. You do not need to save/restore option_mask32,
64 it is already done by core code.
65 * if you allocate memory, you can use xmalloc() only on the very first
66 allocation. All other allocations should use malloc[_or_warn]().
67 After first allocation, you cannot use any xfuncs.
68 Otherwise, failing xfunc will return to caller applet
69 without freeing malloced data!
70 * All allocated data, opened files, signal handlers, termios settings,
71 O_NONBLOCK flags etc should be freed/closed/restored prior to return.
74 NOFORK applets give the most of speed advantage, but are trickiest
75 to implement. In order to minimize amount of bugs and maintenance,
76 prime candidates for NOFORK-ification are those applets which
77 are small and easy to audit, and those which are more likely to be
78 frequently executed from shell/find/xargs, particularly in shell
79 script loops. Applets which mess with signal handlers, termios etc
80 are probably not worth the effort.
82 Any NOFORK applet is also a NOEXEC applet.
85 Calling NOFORK applets
87 API to call NOFORK applets is two functions:
89 run_nofork_applet(appno, argv)
90 spawn_and_wait(argv) // only if FEATURE_PREFER_APPLETS=y
92 First one is directly used by shells if FEATURE_SH_NOFORK=y.
93 Second one is used by many applets, but main users are xargs and find.
94 It itself calls run_nofork_applet(), if argv[0] turned out to be a name
97 run_nofork_applet() saves/inits/restores option parsing, xfunc_error_retval,
98 applet_name. Thus, for example, caller does not need to worry about
99 option_mask32 getting trashed.
102 Calling NOEXEC applets
104 It's the same trusty spawn_and_wait(argv). If FEATURE_PREFER_APPLETS=y,
105 it does NOEXEC trick. It resets xfunc_error_retval = 1 and
106 logmode = LOGMODE_STDIO in the child.
109 Relevant CONFIG options
111 FEATURE_PREFER_APPLETS
112 BB_EXECVP(cmd, argv) will try to exec /proc/self/exe
113 if command's name matches some applet name;
114 spawn_and_wait(argv) will do NOFORK/NOEXEC tricks
116 //TODO: the above two things probably should have separate options?
118 FEATURE_SH_STANDALONE
119 shells will try to exec /proc/self/exe if command's name matches
120 some applet name; shells will do NOEXEC trick on NOEXEC applets
122 //TODO: split (same as for PREFER_APPLETS)
125 shells will do NOFORK trick on NOFORK applets