linux-kernel - Re: 2.6.25-rc2-mm1: WARNING at arch/x86/mm/ioremap.c:129

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: <47C35661.80109@googlemail.com>
Date:	Tue, 26 Feb 2008 00:59:29 +0100
From:	Gabriel C <nix.or.die@...glemail.com>
To:	Arjan van de Ven <arjan@...ux.intel.com>
CC:	Laurent Riffard <laurent.riffard@...e.fr>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Stuart Bennett <sb476@....ac.uk>,
	Len Brown <lenb@...nel.org>
Subject: Re: 2.6.25-rc2-mm1: WARNING at arch/x86/mm/ioremap.c:129

Gabriel C wrote:
> Arjan van de Ven wrote:
>> Gabriel C wrote:
>>> Arjan van de Ven wrote:
>>>> Gabriel C wrote:
>>>>> Laurent Riffard wrote:
>>>>>> Le 16.02.2008 09:25, Andrew Morton a écrit :
>>>>>>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.25-rc2/2.6.25-rc2-mm1/
>>>>> [..]
>>>>>
>>>>> I'm getting that in mainline now on one of my older laptops also.
>>>> we fixed the cause of the machine you quoted; so I suspect yours is different..
>>>> Can you get me your stacktrace ? Can you try the patch from this thread to show
>>>> what memory the offender tries to access ?
>>> Arjan , sorry for the lag.
>>>
>>> With your patch from http://marc.info/?l=linux-kernel&m=120336371506283&w=2 I don't have a warning anymore.
>>>
>> that is ... odd since it's the same in theory, just with some added printk's ;-(
>>
> 
> hmm but in theory only that part of your patch only should do the same , no ?
> 
> 	if (page_is_ram(pfn)) {
> 		printk(..)
> 	}
> 
> I'm going to try that.
> 
> 

With only that part I get the waring again. 

But I see the printk() twice so I guess this should be in general an WARN_ON() ?

http://frugalware.org/~crazy/dmesg/dmesg_with_patch_2

 
--
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/