linux-kernel - Re: [patch] x86_64, vsyscall: fix the oops crash with __pa

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: <200710101536.59156.ak@suse.de>
Date:	Wed, 10 Oct 2007 15:36:58 +0200
From:	Andi Kleen <ak@...e.de>
To:	"Siddha, Suresh B" <suresh.b.siddha@...el.com>
Cc:	akpm@...ux-foundation.org, yanmin.zhang@...el.com,
	vgoyal@...ibm.com, linux-kernel@...r.kernel.org,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [patch] x86_64, vsyscall: fix the oops crash with __pa_vsymbol()

On Wednesday 10 October 2007 03:59:22 Siddha, Suresh B wrote:
> Appended patch fixes an oops while changing the vsyscall sysctl.
> I am sure no one tested this code before integrating into mainline :(

The original code worked, but got broken by 0dbf7028c0c1f266c9631139450a1502d3cd457e
> 
> BTW, using ioremap() in vsyscall_sysctl_change() to get the virtual
> address of a kernel symbol sounds like an over kill.

Another point was to get a writable mapping. At some point we had write 
protected kernels, although that was later then removed again.

> And also, the whole nop out syscall in vsyscall page infrastructure
> (vsyscall_sysctl_change()) is added to make some attacks difficult,
> and yet I don't see this nop out being done by default. This area
> requires more cleanups?

It used to be done, but it is difficult with the changing vreads
in timesources and was probably disabled then. Yes you're right right now 
it looks dubious.

It needs to be updated when the timesource is updated.

-Andi

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