From: Fengguang Wu <fengguang.wu@intel.com>
To: lkp@lists.01.org
Subject: Re: [delayed_fput] BUG: unable to handle kernel paging request at ffff8800122a0ad0
Date: Wed, 30 Jul 2014 20:47:50 +0800 [thread overview]
Message-ID: <20140730124750.GB7717@localhost> (raw)
In-Reply-To: <20140730111521.GB759@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 564 bytes --]
On Wed, Jul 30, 2014 at 04:15:21AM -0700, 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?
The bug is first discovered in linux-next, then the older kernel
releases (v3.15, v3.14, ...) are tested step by step, until it's found
to be introduced between v3.5 and v3.6. Then bisect can be started:
git bisect start v3.6 v3.5 --
Thanks,
Fengguang
WARNING: multiple messages have this Message-ID (diff)
From: Fengguang Wu <fengguang.wu@intel.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: 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
Subject: Re: [delayed_fput] BUG: unable to handle kernel paging request at ffff8800122a0ad0
Date: Wed, 30 Jul 2014 20:47:50 +0800 [thread overview]
Message-ID: <20140730124750.GB7717@localhost> (raw)
In-Reply-To: <20140730111521.GB759@infradead.org>
On Wed, Jul 30, 2014 at 04:15:21AM -0700, 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?
The bug is first discovered in linux-next, then the older kernel
releases (v3.15, v3.14, ...) are tested step by step, until it's found
to be introduced between v3.5 and v3.6. Then bisect can be started:
git bisect start v3.6 v3.5 --
Thanks,
Fengguang
next prev parent reply other threads:[~2014-07-30 12:47 UTC|newest]
Thread overview: 13+ 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 3:55 ` Fengguang Wu
2014-07-30 11:15 ` Christoph Hellwig
2014-07-30 11:15 ` Christoph Hellwig
2014-07-30 12:47 ` Fengguang Wu [this message]
2014-07-30 12:47 ` Fengguang Wu
2014-07-30 22:51 ` David Rientjes
2014-07-30 22:51 ` David Rientjes
2014-07-30 23:00 ` Alexei Starovoitov
2014-07-31 2:40 ` Fengguang Wu
2014-07-31 2:40 ` Fengguang Wu
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=20140730124750.GB7717@localhost \
--to=fengguang.wu@intel.com \
--cc=lkp@lists.01.org \
/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.