From: Fengguang Wu <fengguang.wu@intel.com>
To: John Stultz <johnstul@us.ibm.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()
Date: Tue, 21 Aug 2012 09:40:27 +0800 [thread overview]
Message-ID: <20120821014027.GA12316@localhost> (raw)
In-Reply-To: <5032E114.30503@us.ibm.com>
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.
Thanks,
Fengguang
next prev parent reply other threads:[~2012-08-21 1:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 1:04 BUG: NULL pointer dereference in shmem_evict_inode() Fengguang Wu
2012-08-21 1:10 ` John Stultz
2012-08-21 1:15 ` John Stultz
2012-08-21 1:40 ` Fengguang Wu [this message]
2012-08-21 1:49 ` John Stultz
2012-08-21 8:01 ` Fengguang Wu
2012-08-21 1:31 ` Fengguang Wu
2012-08-21 1:31 ` Fengguang Wu
2012-08-21 1:46 ` John Stultz
2012-08-21 1:58 ` Fengguang Wu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120821014027.GA12316@localhost \
--to=fengguang.wu@intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=johnstul@us.ibm.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=prarit@redhat.com \
--cc=richardcochran@gmail.com \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.