mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Christian Kujau <lists@nerdbynature.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
	akpm@linux-foundation.org,
	nico-linuxsetlocalversion@schottelius.org
Subject: Re: [PATCH] scripts/setlocalversion on write-protected source tree
Date: Mon, 24 Jun 2013 00:10:55 +0200	[thread overview]
Message-ID: <20130623221055.GA16118@pobox.suse.cz> (raw)
In-Reply-To: <alpine.DEB.2.10.1306141756510.13746@trent.utfs.org>

On Fri, Jun 14, 2013 at 06:04:34PM -0700, Christian Kujau wrote:
> 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.

Applied to kbuild.git#kbuild.

Thanks,
Michal

      reply	other threads:[~2013-06-23 22:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-15  1:04 Christian Kujau
2013-06-23 22:10 ` Michal Marek [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130623221055.GA16118@pobox.suse.cz \
    --to=mmarek@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@nerdbynature.de \
    --cc=nico-linuxsetlocalversion@schottelius.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®