linux-kernel - Re: [git head] Should X86_PAT really default to yes?

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]

Date:	Sun, 25 May 2008 17:08:47 +0200
From:	Frans Pop <elendil@...net.nl>
To:	Venki Pallipadi <venkatesh.pallipadi@...el.com>
Cc:	Jesse Barnes <jesse.barnes@...el.com>,
	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
	"Packard, Keith" <keith.packard@...el.com>,
	Yinghai Lu <yhlu.kernel@...il.com>
Subject: Re: [git head] Should X86_PAT really default to yes?

On Wednesday 07 May 2008, Venki Pallipadi wrote:
> On Mon, May 05, 2008 at 07:32:40PM +0200, Frans Pop wrote:
> > Note that the "expected mapping type" errors remain the same both with
> > and without framebuffer console.
>
> The patch below plugs the mprotect hole and should eliminate the
> "expected mapping type" error messages. Can you check.

Hi,

My apologies for the very late reply. Unfortunately I've had no time for 
work on kernel issues the last few weeks.

I have not specifically tested any of the proposed patches, but I can 
confirm that the "expected mapping type" errors are gone with -rc2 
and -rc3. Thanks a lot.

The artifacts are still there though and frequently even worse than 
originally reported. I will open a bugzilla entry for that.

Cheers,
FJP
--
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/