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: <CAD=FV=U4WxMLyEAgGExc=Q7r9jy=AS3mtxSoi=M+Qgw_e=U-bg@mail.gmail.com>
Date:	Wed, 23 Apr 2014 15:51:45 -0700
From:	Doug Anderson <dianders@...gle.com>
To:	Kees Cook <keescook@...omium.org>
Cc:	Rabin Vincent <rabin@....in>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Laura Abbott <lauraa@...eaurora.org>,
	Jon Medhurst <tixy@...aro.org>
Subject: Re: [PATCH 2/2] arm: use fixmap for text patching when text is RO

Kees,

On Wed, Apr 23, 2014 at 2:09 PM, Kees Cook <keescook@...omium.org> wrote:

> I think we can use this for the kgdb case too. Has anyone tried that
> yet? Perhaps implementing text_poke() in terms of patch_map/unmap
> calls would be best? Then the arm-specific kgdb hooks can use that,
> since it does the icache flushing separately.

Yes.  I just tried using these patches and it worked for me.  :)  I
didn't actually implement text_poke(), though.

Atop our 3.8 tree, in case anyone is curious

* https://chromium-review.googlesource.com/196670
* https://chromium-review.googlesource.com/196671
* https://chromium-review.googlesource.com/196672
* https://chromium-review.googlesource.com/196673
* https://chromium-review.googlesource.com/196674

Please include me on the CC list for spins of your patches...

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ