From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752511AbbD3SAE (ORCPT ); Thu, 30 Apr 2015 14:00:04 -0400 Received: from mail-ig0-f170.google.com ([209.85.213.170]:38750 "EHLO mail-ig0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751085AbbD3SAA (ORCPT ); Thu, 30 Apr 2015 14:00:00 -0400 MIME-Version: 1.0 In-Reply-To: References: <20150430135843.20271.47526.stgit@warthog.procyon.org.uk> <21274.1430405427@warthog.procyon.org.uk> Date: Thu, 30 Apr 2015 11:00:00 -0700 X-Google-Sender-Auth: M1hL8SLvMdUKnHkGh-al9vbXHsI Message-ID: Subject: Re: [PATCH] MODSIGN: Change default key details [ver #2] From: Linus Torvalds To: Sedat Dilek Cc: David Howells , keyrings@linux-nfs.org, Rusty Russell , LKML , LSM List , James Morris , Greg Kroah-Hartman Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Apr 30, 2015 at 10:49 AM, Sedat Dilek wrote: >> >> Yeah. I've had other reports, but I can't see anything obvious. I have a >> suspicion there may be something not declared quite right in the makefile - or >> even a race in make -jN, but I don't know how to reproduce it. > > Ah OK, (un)nice to read. Yeah. I've gotten "X.509 certificate list changed" messages occasionally, which makes no sense considering that I never have any keys except for the default signing key. So there is something odd foinf on with "kernel/.x509.list". The rules to generate it aren't really _rules_. It's black magic. Actually, it's *generated* with a rule, but then it has that magical "if the contents don't match" thing that is _not_ a real make rule. It would be lovely to replace that with a real "if_changed" rule, because I do think the magic hackery is what the confuses make. Maybe some concurrent build reads the file - to check if it's the same - in one make instance while it's being generated in another. Something. [ Wild handwaving going on ]. Linus