linux-kernel - Re: [PATCH] x86, PAT: honor CONFIG_STRICT

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] [day] [month] [year] [list]

Date:	Sat, 23 Jul 2011 14:39:51 +0200
From:	Michal Hocko <mhocko@...e.cz>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Venkatesh Pallipadi <venki@...gle.com>, x86@...nel.org,
	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>
Subject: Re: [PATCH] x86, PAT: honor CONFIG_STRICT_DEVMEM if pat is disable]

On Fri 22-07-11 11:30:55, H. Peter Anvin wrote:
> On 07/22/2011 10:31 AM, Michal Hocko wrote:
> > 
> > Thanks for the clarification!
> > What do you think about fixing the nopat with STRICT_DEVMEM like the
> > patch does?
> > 
> 
> From what I gather from your patch, the issue is that STRICT_DEVMEM
> isn't being honored with nopat?

Yes.

> This is an obvious bug and should be fixed.

OK, thanks for confirmation. Should I just repost the patch without the
question about PAT vs. /dev/[k]mem or you will just pick it up from
there? Or would you preffer a different fix?

Thanks
-- 
Michal Hocko
SUSE Labs
SUSE LINUX s.r.o.
Lihovarska 1060/12
190 00 Praha 9    
Czech Republic
--
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/