From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755455AbaFYUGv (ORCPT ); Wed, 25 Jun 2014 16:06:51 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:47175 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752271AbaFYUGt (ORCPT ); Wed, 25 Jun 2014 16:06:49 -0400 Date: Wed, 25 Jun 2014 13:06:48 -0700 From: Andrew Morton To: Ian Kent Cc: linux-fsdevel , autofs mailing list , Kernel Mailing List Subject: Re: [PATCH] autofs4 - fix false positive compile error Message-Id: <20140625130648.1e3cd0e578602918dc38bb6a@linux-foundation.org> In-Reply-To: <20140625124939.31035.84884.stgit@perseus.fritz.box> References: <20140625124939.31035.84884.stgit@perseus.fritz.box> X-Mailer: Sylpheed 3.2.0beta5 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 25 Jun 2014 20:49:39 +0800 Ian Kent wrote: > On strict build environments we can see: > > fs/autofs4/inode.c: In function 'autofs4_fill_super': > fs/autofs4/inode.c:312: error: 'pgrp' may be used uninitialized in this > function > make[2]: *** [fs/autofs4/inode.o] Error 1 > make[1]: *** [fs/autofs4] Error 2 > make: *** [fs] Error 2 > make: *** Waiting for unfinished jobs.... > > This is due to the use of pgrp_set being used to indicate pgrp has > has been set rather than initializing pgrp itself. > Yes, that code seems to be explicitly designed to trigger a gcc warning ;) What is a "strict build environment"? Someone's using -Werror for the entire kernel? That must make for a miserable life.