Skip to content

Commit cdf2bc6

Browse files
ckujaumichal42
authored andcommitted
scripts/setlocalversion on write-protected source tree
I just stumbled across another[0] issue when scripts/setlocalversion operates on a write-protected source tree. Back then[0] the source tree was on an read-only NFS share, so "test -w" was introduced before "git update-index" was run. This time, the source tree is on read/write NFS share, but the permissions are world-readable and only a specific user (or root) can write. Thus, "test -w ." returns "0" and then runs "git update-index", producing the following message (on a dirty tree): fatal: Unable to create '/usr/local/src/linux-git/.git/index.lock': Permission denied While it says "fatal", compilation continues just fine. However, I don't think a kernel compilation should alter the source tree (or the .git directory) in any way and I don't see how removing "git update-index" could do any harm. The Mercurial and SVN routines in scripts/setlocalversion don't have any tree-modifying commands, AFAICS. So, maybe the patch below would be acceptable. [0] https://patchwork.kernel.org/patch/29718/ Signed-off-by: Christian Kujau <lists@nerdbynature.de> Cc: Nico Schottelius <nico-linuxsetlocalversion@schottelius.org> Signed-off-by: Michal Marek <mmarek@suse.cz>
1 parent 1c00a47 commit cdf2bc6

File tree

1 file changed

+0
-3
lines changed

1 file changed

+0
-3
lines changed

scripts/setlocalversion

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -71,9 +71,6 @@ scm_version()
7171
printf -- '-svn%s' "`git svn find-rev $head`"
7272
fi
7373

74-
# Update index only on r/w media
75-
[ -w . ] && git update-index --refresh --unmerged > /dev/null
76-
7774
# Check for uncommitted changes
7875
if git diff-index --name-only HEAD | grep -qv "^scripts/package"; then
7976
printf '%s' -dirty

0 commit comments

Comments
 (0)