linux-kernel - Re: [PATCH] ARM: probes: Don't stop the machine if we're in the debugger

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

Message-ID: <CAD=FV=WDJ3-QimHA56nc3rg7T_aGqW2kw+BBW7zMye_6VfqeVg@mail.gmail.com>
Date:	Tue, 25 Aug 2015 15:08:07 -0700
From:	Doug Anderson <dianders@...omium.org>
To:	Stephen Boyd <sboyd@...eaurora.org>
Cc:	Kees Cook <keescook@...omium.org>, Nicolas Pitre <nico@...aro.org>,
	Jon Medhurst <tixy@...aro.org>, wangnan0 <wangnan0@...wei.com>,
	Russell King <linux@....linux.org.uk>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Aapo Vienamo <avienamo@...dia.com>,
	Rabin Vincent <rabin@....in>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH] ARM: probes: Don't stop the machine if we're in the debugger

Hi,

On Mon, Aug 24, 2015 at 5:19 PM, Stephen Boyd <sboyd@...eaurora.org> wrote:
> Can you add the backtrace?

Good point.  Done.

> Perhaps it would be better to add a different function for the kgdb call
> site? Then it's explicit what's going on without us having to figure out
> when in_dbg_master() is true.

Actually, there was already a function to patch the text directly
without stopping the machine.  :)

Adding a bit of extra noise here to point to my new patch since it has
a very different title than this one (so might be hard to find).  See
<https://patchwork.kernel.org/patch/7073441/>.

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