Message-ID: <5032E85D.8020404@linaro.org>
Date: Mon, 20 Aug 2012 18:46:05 -0700
From: John Stultz <john.stultz@linaro.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0
MIME-Version: 1.0
To: Fengguang Wu <fengguang.wu@intel.com>
CC: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@kernel.org>,
        Peter Zijlstra <a.p.zijlstra@chello.nl>,
        Richard Cochran <richardcochran@gmail.com>,
        Prarit Bhargava <prarit@redhat.com>,
        Thomas Gleixner <tglx@linutronix.de>, linux-fsdevel@vger.kernel.org
Subject: Re: BUG: NULL pointer dereference in shmem_evict_inode()
References: <20120821010403.GA12018@localhost> <5032E021.2030400@linaro.org> <20120821013123.GA12104@localhost>
In-Reply-To: <20120821013123.GA12104@localhost>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1719
Lines: 37

On 08/20/2012 06:31 PM, Fengguang Wu wrote:
> On Mon, Aug 20, 2012 at 06:10:57PM -0700, 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.
> That's great!
>
>> Out of curiosity, how are you triggering/reproducing this?
> I boot test lots of randconfig kernels in kvm, and this oops shows up
> several times in one ranconfig and some of the test boxes. I find it
> pretty hard to reproduce, but managed to bisect it down by counting
> 1000 good boots as bisect success and running dozens of KVM instances
> in parallel in several test boxes to speed up the progress. Here is one step:

Oof.  That's an really impressive setup!

That said, if this happens only at boot up, and you don't have systems 
with crazy cmos values, I'm not sure I see how commit 
4e8b14526ca7fb046a81c94002c1c43b6fdf0e9b might fix this.  So that's not 
very reassuring.

As a tangent, I think this sort of big-data style testing is a really 
great contribution, so thank you for setting up and doing all this work.
-john

--
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/