From: Fengguang Wu <fengguang.wu@intel.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: David Rientjes <rientjes@google.com>,
Christoph Hellwig <hch@infradead.org>,
Al Viro <viro@zeniv.linux.org.uk>, Jet Chen <jet.chen@intel.com>,
Su Tao <tao.su@intel.com>, Yuanhan Liu <yuanhan.liu@intel.com>,
LKP <lkp@01.org>,
linux-fsdevel@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [delayed_fput] BUG: unable to handle kernel paging request at ffff8800122a0ad0
Date: Thu, 31 Jul 2014 10:40:14 +0800 [thread overview]
Message-ID: <20140731024014.GA10184@localhost> (raw)
In-Reply-To: <CAADnVQ+OwgG-RJQ7QwfW2qrvpV9XYySckTbNmcacW7K0KxQqvA@mail.gmail.com>
On Wed, Jul 30, 2014 at 04:00:58PM -0700, Alexei Starovoitov wrote:
> On Wed, Jul 30, 2014 at 3:51 PM, David Rientjes <rientjes@google.com> wrote:
> > On Wed, 30 Jul 2014, Christoph Hellwig wrote:
> >
> >> On Wed, Jul 30, 2014 at 11:55:41AM +0800, Fengguang Wu wrote:
> >> > Greetings,
> >> >
> >> > 0day kernel testing robot got the below dmesg and the first bad commit is
> >>
> >> How does this manage to trip over a 2 year old commit now?
>
> may be because all kernels are built with gcc 4.8.2 ?
> Fengguang, did you recently switch to new compiler?
> I think all older builds were with 4.6.3
Alexei, I've been using gcc 4.8.2 for 4 months.
Maybe it's because I test new randconfigs every day. And the problem
may only show up with very specific kernel config?
Thanks,
Fengguang
> > I think there's something weird going on with the testing of CONFIG_SLOB,
> > same as http://permalink.gmane.org/gmane.linux.kernel/1759314 that
> > identified a harmless commit that only initializes a field of
> > struct mm_struct and then ended up exploded in slob freeing.
> > --
> > 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/
next prev parent reply other threads:[~2014-07-31 2:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 3:55 [delayed_fput] BUG: unable to handle kernel paging request at ffff8800122a0ad0 Fengguang Wu
2014-07-30 11:15 ` Christoph Hellwig
2014-07-30 12:47 ` Fengguang Wu
2014-07-30 22:51 ` David Rientjes
2014-07-30 23:00 ` Alexei Starovoitov
2014-07-31 2:40 ` Fengguang Wu [this message]
2014-07-31 2:53 ` Alexei Starovoitov
2014-07-31 10:27 ` 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=20140731024014.GA10184@localhost \
--to=fengguang.wu@intel.com \
--cc=alexei.starovoitov@gmail.com \
--cc=hch@infradead.org \
--cc=jet.chen@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=rientjes@google.com \
--cc=tao.su@intel.com \
--cc=viro@zeniv.linux.org.uk \
--cc=yuanhan.liu@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).