linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: WARNING: at lib/debugobjects.c:261 debug_print_object()
Date: Mon, 11 Feb 2013 21:25:56 +0800	[thread overview]
Message-ID: <20130211132556.GA16137@localhost> (raw)
In-Reply-To: <20130211111714.5e6fa4c8dc9c0d99cb1c1de1@canb.auug.org.au>

On Mon, Feb 11, 2013 at 11:17:14AM +1100, Stephen Rothwell wrote:
> Hi Fengguang,
> 
> On Fri, 8 Feb 2013 13:56:05 +0800 Fengguang Wu <fengguang.wu@intel.com> wrote:
> >
> > I got the below oops and the first bad commit is
> > 
> > commit 457583af4aef89d5252769ea290a2acc89e2361f
> > Author: Stephen Rothwell <sfr@canb.auug.org.au>
> > Date:   Mon Feb 4 18:12:17 2013 +1100
> > 
> >     memory-hotplug: common APIs to support page tables hot-remove fix fix
> >     
> >     Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
> > 
> > I see no direct relationship between the change and oops message,
> > however I tried two bisects and they both converge to the above
> > commit.
> 
> Thanks for the report.
> 
> Did reverting just that commit fix the problem?  Is it still a problem in
> next-20130208?

Stephen, build failed after reverting the commit, however next-20130208
no longer has the problem. So we may probably forget about it.

Thanks,
Fengguang

  reply	other threads:[~2013-02-11 13:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-08  5:56 WARNING: at lib/debugobjects.c:261 debug_print_object() Fengguang Wu
2013-02-11  0:17 ` Stephen Rothwell
2013-02-11 13:25   ` Fengguang Wu [this message]
2013-02-11 20:18     ` Stephen Rothwell

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=20130211132556.GA16137@localhost \
    --to=fengguang.wu@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).