Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933440Ab0DHUNJ (ORCPT ); Thu, 8 Apr 2010 16:13:09 -0400 Received: from 74-93-104-97-Washington.hfc.comcastbusiness.net ([74.93.104.97]:59568 "EHLO sunset.davemloft.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758758Ab0DHUNC (ORCPT ); Thu, 8 Apr 2010 16:13:02 -0400 Date: Thu, 08 Apr 2010 13:13:04 -0700 (PDT) Message-Id: <20100408.131304.166360041.davem@davemloft.net> To: tony.luck@intel.com Cc: timo.teras@iki.fi, sfr@canb.auug.org.au, netdev@vger.kernel.org, linux-next@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: linux-next: powerpc boot failure From: David Miller In-Reply-To: References: <20100408174549.2f45ceea.sfr@canb.auug.org.au> <4BBD966D.8020404@iki.fi> X-Mailer: Mew version 6.3 on Emacs 23.1 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-7 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by alpha.home.local id o38KDfmE020446 Content-Length: 788 Lines: 20 From: Tony Luck Date: Thu, 8 Apr 2010 11:55:34 -0700 > I tried the patch you just posted. Compiling with it gave this warning: > > net/xfrm/xfrm_policy.c: In function ?__xfrm_lookup?: > net/xfrm/xfrm_policy.c:1735: warning: ?num_xfrms? may be used > uninitialized in this function This is just because gcc is stupid, you can ignore this. It can't see that when a real 'err' error is returned we never end up referencing the num_xfrms value. > but the patched kernel booted ok. Thanks for testing, I pushed Timo's fix to net-next-2.6 earlier today so it'll hopefully show up in the next linux-next. ????{.n?+???????+%?????ݶ??w??{.n?+????{??G?????{ay?ʇڙ?,j??f???h?????????z_??(?階?ݢj"???m??????G????????????&???~???iO???z??v?^?m???? ????????I?