linux-kernel - RE: [patch 0/4] x86: PAT followup - Incremental changes and bug fixes

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: <924EFEDD5F540B4284297C4DC59F3DEE5E8C86@orsmsx423.amr.corp.intel.com>
Date:	Wed, 16 Jan 2008 14:14:40 -0800
From:	"Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com>
To:	"Andi Kleen" <ak@....de>
Cc:	"Andreas Herrmann" <andreas.herrmann3@....com>,
	<ebiederm@...ssion.com>, <rdreier@...co.com>,
	<torvalds@...ux-foundation.org>, <gregkh@...e.de>,
	<airlied@...net.ie>, <davej@...hat.com>, <mingo@...e.hu>,
	<tglx@...utronix.de>, <hpa@...or.com>, <akpm@...ux-foundation.org>,
	<arjan@...radead.org>, "Barnes, Jesse" <jesse.barnes@...el.com>,
	<davem@...emloft.net>, <linux-kernel@...r.kernel.org>,
	"Siddha, Suresh B" <suresh.b.siddha@...el.com>
Subject: RE: [patch 0/4] x86: PAT followup - Incremental changes and bug fixes

 

>-----Original Message-----
>From: Andi Kleen [mailto:ak@....de] 
>Sent: Wednesday, January 16, 2008 2:02 PM
>To: Pallipadi, Venkatesh
>Cc: Andreas Herrmann; ebiederm@...ssion.com; 
>rdreier@...co.com; torvalds@...ux-foundation.org; 
>gregkh@...e.de; airlied@...net.ie; davej@...hat.com; 
>mingo@...e.hu; tglx@...utronix.de; hpa@...or.com; 
>akpm@...ux-foundation.org; arjan@...radead.org; Barnes, Jesse; 
>davem@...emloft.net; linux-kernel@...r.kernel.org; Siddha, Suresh B
>Subject: Re: [patch 0/4] x86: PAT followup - Incremental 
>changes and bug fixes
>
>> This ioremap failing seems to be the real problem. This can be due to
>> new tracking of ioremaps introduced by PAT patches. We do not allow
>> conflicting ioremaps to same region. Probably that is happening
>
>Normally if there is a conflict there should be a printk (or 
>at least it was
>so in the original mattr code if you haven't changed it)
>

Yes. Printks are there. But are with KERN_DEBUG now. We should change
them to WARNING atleast.

Thanks,
Venki
--
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/