From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Stultz Subject: Re: BUG: NULL pointer dereference in shmem_evict_inode() Date: Mon, 20 Aug 2012 18:15:00 -0700 Message-ID: <5032E114.30503@us.ibm.com> References: <20120821010403.GA12018@localhost> <5032E021.2030400@linaro.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: LKML , Ingo Molnar , Peter Zijlstra , Richard Cochran , Prarit Bhargava , Thomas Gleixner , linux-fsdevel@vger.kernel.org To: Fengguang Wu Return-path: In-Reply-To: <5032E021.2030400@linaro.org> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org 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. thanks -john