linux-kernel - Re: WARNING: at lib/debugobjects.c:261 debug_print

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130211132556.GA16137@localhost>
Date:	Mon, 11 Feb 2013 21:25:56 +0800
From:	Fengguang Wu <fengguang.wu@...el.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: WARNING: at lib/debugobjects.c:261 debug_print_object()

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@...el.com> wrote:
> >
> > I got the below oops and the first bad commit is
> > 
> > commit 457583af4aef89d5252769ea290a2acc89e2361f
> > Author: Stephen Rothwell <sfr@...b.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@...b.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/