linux-kernel - Re: WARNING: CPU: 2 PID: 1 at arch/x86/mm/ioremap.c:171 __ioremap

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20140709185421.GB20302@kroah.com>
Date:	Wed, 9 Jul 2014 11:54:21 -0700
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Fabio Coatti <fabio.coatti@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: WARNING: CPU: 2 PID: 1 at arch/x86/mm/ioremap.c:171
 __ioremap_caller+0x290/0x2fa()

On Wed, Jul 09, 2014 at 08:41:17PM +0200, Fabio Coatti wrote:
> In data lunedì 7 luglio 2014 13:47:47, Greg Kroah-Hartman ha scritto:
> > On Mon, Jul 07, 2014 at 10:32:56PM +0200, Fabio Coatti wrote:
> > > I'm seeing this message in latest kernels (this is from 3.15.4, but I have
> > > same
> > > message starting from 3.15.0, IIRC):
> > So 3.14.0 didn't show this?
> > 
> > If so, can you run 'git bisect' between those two kernel versions to try
> > to track down the issue?
> > 
> > thanks,
> > 
> > greg k-h
> ok, I tried to bisect as suggested and got the commit reported below. However 
> I'm not really sure to have got the right one, as one kernel refused to 
> compile during the last steps. However I post here the result, maybe they can 
> be useful.

Try cc:ing everyone on that patch, with the original information you
provided, and the linux-kernel mailing list.  Those developers should be
able to help you out properly.

thanks,

greg k-h
--
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/