2bef52633
Denys Vlasenko
2011-12-16
Subject
ash: add comment about bash's ENOEXEC handling. No code changes
Binary
No binary (build failed)
Architecture & Compiler Flags
—
Build Log
(log yok)
Commit Diff GitHub →
shell/ash.c+6 -0
| @@ -7435,6 +7435,12 @@ tryexec(IF_FEATURE_SH_STANDALONE(int applet_no,) char *cmd, char **argv, char ** | |
| * | |
| * That is, do not use $SHELL, user's shell, or /bin/sh; | |
| * just call ourselves. | |
| + | * |
| + | * Note that bash reads ~80 chars of the file, and if it sees |
| + | * a zero byte before it sees newline, it doesn't try to |
| + | * interpret it, but fails with "cannot execute binary file" |
| + | * message. For one, it prevents atempts to interpret |
| + | * foreign ELF binaries as shell scripts. |
| */ | |
| char **ap; | |
| char **new; | |