Summary: | sys-kernel/vanilla-sources-4.14.10: execvp: ./sync-check.sh: Permission denied | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Ulenrich <ulenrich> |
Component: | Current packages | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | bugs, jkt, krinpaus, manday, rose |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Ulenrich
2017-12-30 02:15:40 UTC
Disabling the GCC latent_entropy_plugin - same result Whats interesting: As I make the kernel as root there should no be no problem with permissions --- # vdir $(find . -name sync-check.sh) -rw-r--r-- 1 root root 0 30. Dez 02:54 ./.pc/arelease/patch-4.14.10/tools/objtool/sync-check.sh -rw-r--r-- 1 root root 584 30. Dez 02:54 ./tools/objtool/sync-check.sh --- I am clueless. Never happened to me failing to compile the kernel. Same here. Execution flags are missing and # chmod 755 /tools/objtool/sync-check.sh seems to fix it. According to https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/log/tools/objtool/sync-check.sh sync-check.sh should have +x already set. Does Gentoo apply any changes to this? The reason why sync-check.sh doesn't have the necessary permission is apparently that the incremental patch from 4.14 to 4.14.10 does *not* correctly set permissions:
> diff --git a/tools/objtool/sync-check.sh b/tools/objtool/sync-check.sh
> new file mode 100755
> index 000000000000..1470e74e9d66
> --- /dev/null
> +++ b/tools/objtool/sync-check.sh
> @@ -0,0 +1,29 @@
> +#!/bin/sh
> ...
After applying this patch to the 4.14 sources, sync-check.sh appears, but without +x permissions.
@Cedric, I didn't dare to # chmod 755 tools/objtool/sync-check.sh because of the strange error message: "make[2]: execvp: ./sync-check.sh: Permission denied" I don't know "execvp" I looked into patch-4.14.10: # grep -A 3 -e'^new file mode' patch-4.14.10|grep -B 3 -e'sync-check.sh' new file mode 100755 index 000000000000..1470e74e9d66 --- /dev/null +++ b/tools/objtool/sync-check.sh The issue is a missing feature of sys-devel/patch-2.7.5 The patch utility does not bother about file mode of sync-check.sh It only can set a standard 644 mode Downloading the full patche kernel.org source https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.14.10.tar.xz also shows correcty set execution file mode of sync-check.sh These days all people use git not patch any more :( *** This bug has been marked as a duplicate of bug 642664 *** This still happens with vanilla-sources (checked with 4.14.10 renamed to 4.14.11 which isn't in the tree yet, but that doesn't matter). A change in gentoo-specific patches doesn't help, so I'm marking this as non-duplicate. this patch is not solving the problem ? http://www.ozlabs.org/~akpm/mmotm/broken-out/tools-objtool-makefile-dont-assume-sync-checksh-is-executable.patch (In reply to Alice Ferrazzi from comment #9) > this patch is not solving the problem ? > http://www.ozlabs.org/~akpm/mmotm/broken-out/tools-objtool-makefile-dont- > assume-sync-checksh-is-executable.patch It looks like it should solve the problem. However, it isn't present in the v4.14.11, and also not in the patch that the Gentoo ebuilds of vanilla-sources are using. Gentoo kernel team cannot support vanilla-sources. I see the same issue now with vanilla-sources-4.14.12. Official patch on the Kernel list for the 'linux-next' branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20171222&id=9d641b18db295b9ded33df0430940c7df7bb795e Kernel Bugzilla listing: https://bugzilla.kernel.org/show_bug.cgi?id=198361 And it happens again with vanilla-sources-4.14.13. The same happens with vanilla-sources-4.14.14: * LD /usr/src_lynx/linux-4.14.14/tools/objtool/objtool-in.o *make[2]: execvp: ./sync-check.sh: Permission denied *make[2]: *** [Makefile:49: /usr/src_lynx/linux-4.14.14/tools/objtool/objtool] Error 127 *make[1]: *** [Makefile:62: objtool] Error 2 Per Kernel.org at https://bugzilla.kernel.org/show_bug.cgi?id=198361 4.14.15 has this bug fixed. Please close. (In reply to Kelly Price from comment #16) > Per Kernel.org at https://bugzilla.kernel.org/show_bug.cgi?id=198361 > > 4.14.15 has this bug fixed. Please close. The bug has been closed for almost three weeks; it never belonged on a Gentoo bug tracker as it is/was an upstream issue. |