From: Michael Ellerman <michael@ellerman.id.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux-Next <linux-next@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: ccache: FATAL: Could not create /scratch/kisskb/ccache
Date: Wed, 05 Dec 2012 18:53:09 +1100 [thread overview]
Message-ID: <1354693989.27132.3.camel@concordia> (raw)
In-Reply-To: <CAMuHMdWeDsAtmUq_TEFRAEY_gikAVoh=-mqwwp9OzOXobyWo+A@mail.gmail.com>
On Wed, 2012-11-14 at 09:03 +0100, Geert Uytterhoeven wrote:
> Hi Stephen,
>
> On Sat, Nov 3, 2012 at 12:19 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > On Fri, 2 Nov 2012 19:44:48 +0100 Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> >> http://kisskb.ellerman.id.au/kisskb/buildresult/7458505/
> >>
> >> ccache: FATAL: Could not create
> >> /scratch/kisskb/ccache/d/7/f9e308f728ef43aaa482aefb9a00a2-852386.o.tmp.stdout.Sprygo.5748
> >> (permission denied?)
> >> make[4]: *** [drivers/media/rc/ene_ir.o] Error 1
> >>
> >> http://kisskb.ellerman.id.au/kisskb/buildresult/7461979/
> >>
> >> ccache: FATAL: Could not create
> >> /scratch/kisskb/ccache/5/e/47d893acad42c07542edec1f826579-1842636.o.tmp.stdout.Sprygo.557
> >> (permission denied?)
> >> make[3]: *** [net/core/sock.o] Error 1
> >
> > Well, that is weird. I can't find any reason for that to happen :-(
> >
> > I'll have a chat with the kisskb guy when I next see him. Thanks for the
> > heads up.
>
> As code is migrating to Linus' tree, it's spreading from the linux-next to the
> linus branch, e.g.:
> http://kisskb.ellerman.id.au/kisskb/buildresult/7536268/
> ccache: FATAL: Could not create
> /scratch/kisskb/ccache/1/3/a44cddb2457ad89fe496b0c82b0a09-1211932.o.tmp.stdout.Sprygo.2788
> (permission denied?)
> make[3]: *** [drivers/block/aoe/aoecmd.o] Error 1
Hi Geert,
This has started happening because of a change in ccache (v3.1.7). It
has always checked that the stdout file exists (via stat), but
previously if it was missing it would fall back to a full compile,
whereas now it is a fatal error.
However looking at the ccache code it makes no sense for the file not to
exist, because we just created it. So it's a bit of a mystery.
At the moment I'm running with a slightly hacked ccache (too much and
the bug vanishes), and auditing enabled, to try and work out if someone
is actually unlinking the file or what.
Hopefully we can sort it out in the next few days.
cheers
prev parent reply other threads:[~2012-12-05 7:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-02 18:44 ccache: FATAL: Could not create /scratch/kisskb/ccache Geert Uytterhoeven
2012-11-02 23:19 ` Stephen Rothwell
2012-11-14 8:03 ` Geert Uytterhoeven
2012-12-05 7:53 ` Michael Ellerman [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=1354693989.27132.3.camel@concordia \
--to=michael@ellerman.id.au \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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