Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753445Ab2HUICe (ORCPT ); Tue, 21 Aug 2012 04:02:34 -0400 Received: from mga01.intel.com ([192.55.52.88]:36323 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752331Ab2HUIC2 (ORCPT ); Tue, 21 Aug 2012 04:02:28 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.77,801,1336374000"; d="scan'208";a="207250386" Date: Tue, 21 Aug 2012 16:01:58 +0800 From: Fengguang Wu To: John Stultz Cc: LKML , Ingo Molnar , Peter Zijlstra , Richard Cochran , Prarit Bhargava , Thomas Gleixner , linux-fsdevel@vger.kernel.org Subject: Re: BUG: NULL pointer dereference in shmem_evict_inode() Message-ID: <20120821080158.GA17300@localhost> References: <20120821010403.GA12018@localhost> <5032E021.2030400@linaro.org> <5032E114.30503@us.ibm.com> <20120821014027.GA12316@localhost> <5032E940.3020801@us.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5032E940.3020801@us.ibm.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1706 Lines: 41 On Mon, Aug 20, 2012 at 06:49:52PM -0700, John Stultz wrote: > On 08/20/2012 06:40 PM, Fengguang Wu wrote: > >On Mon, Aug 20, 2012 at 06:15:00PM -0700, John Stultz wrote: > >>On 08/20/2012 06:10 PM, John Stultz wrote: > >>>On 08/20/2012 06:04 PM, Fengguang Wu wrote: > >>>>Hi John, > >>>> > >>>>The below oops happens in v3.5..v3.6-rc2 and it's bisected down > >>>>to commit > >>>>2a8c0883c ("time: Move xtime_nsec adjustment underflow handling > >>>>timekeeping_adjust"). > >>>> > >>>>However linux-next is working fine. Do you have any fixes not > >>>>yet sent to Linus? > >>>Yea, there's a fix pending in tip/timers/urgent > >>>(4e8b14526ca7fb046a81c94002c1c43b6fdf0e9b) to catch crazy values > >>>from settimeofday or the cmos clock that might overflow a ktime_t. > >>>Out of curiosity, how are you triggering/reproducing this? > >>> > >>Looking at the commit you pointed out, it seems more likely Ingo's > >>fix (1d17d17484d40f2d5b35c79518597a2b25296996) might be related, but > >>that should have landed in v3.6-rc2. So I'm not sure. > >Ah ok, looking back into the logs, I didn't find v3.6-rc2 being > >tested. Sorry I should have confused it with another bug. > > > >I'll test v3.6-rc2. > Ok. If v3.6-rc2 doesn't show the problem that would make me feel a > bit better that Ingo's fix is the one that is resolving this for > you. Got the results: v3.6-rc2 tests fine. So it's a fixed problem in the upstream. Sorry for the noises! Thanks, Fengguang -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/