linux-kernel - Re: [PATCH] Add a text

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: <52968018.5090907@zytor.com>
Date:	Wed, 27 Nov 2013 15:28:24 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
CC:	Andy Lutomirski <luto@...capital.net>,
	Andi Kleen <andi@...stfloor.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...nel.org>,
	Andi Kleen <ak@...ux.intel.com>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH] Add a text_poke syscall v2

On 11/27/2013 03:15 PM, Linus Torvalds wrote:
> 
> Oh, I agree. The interface of the original patch was just inane/insane.
> 
> The timeout and the callback is pointless. The only thing the system
> call should get as an argument is the address and the replacement
> instruction.  So
> 
>   int text_poke(void *addr, const void *opcode, size_t len)
> 
> sounds fine to me. And it would do:
>  - take some (possibly per-mm) mutex
>  - write the one-byte int3
>  - do the IPI
>  - write the other bytes
>  - do the IPI
>  - do the first byte
>  - release the (possibly per-mm) mutex
> 
> and then in the BP handler we'd just take the mutex, see if the first
> byte of the exception is still int3, if it's not, just return silently
> (because that means that we hit the race).
> 

I was going to say we can just re-execute the instruction until it goes
away, but this is unsafe for user space since you might have CD 03
(INT 3) somewhere instead of CC (INT3) and backing up to the previous
byte would be bad in the former case.

Even if matched against patch sites it would be iffy.

> Hmm? It doesn't sound too bad. And I really don't see the point of
> some timeout handling or anything like that.

The timeout bit was an acknowledgment that some kind of batching
interface is necessary.  If you are doing this for function tracing, for
example, you can easily have a hundred thousand patch sites or more, and
you may not want to have to go through this process anew for each single
site.  Hence my earlier comment about feeling that we would need a
batched interface of some sort.  Which, unfortunately, has its own set
of problems relating to restartability and potential delay.

	-hpa

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