[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4F3D73E3.7070409@zytor.com>
Date: Thu, 16 Feb 2012 13:23:47 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: Markus Gutschke <markus@...omium.org>
CC: Will Drewry <wad@...omium.org>, linux-kernel@...r.kernel.org,
linux-arch@...r.kernel.org, linux-doc@...r.kernel.org,
kernel-hardening@...ts.openwall.org, netdev@...r.kernel.org,
x86@...nel.org, arnd@...db.de, davem@...emloft.net,
mingo@...hat.com, oleg@...hat.com, peterz@...radead.org,
rdunlap@...otime.net, mcgrathr@...omium.org, tglx@...utronix.de,
luto@....edu, eparis@...hat.com, serge.hallyn@...onical.com,
djm@...drot.org, scarybeasts@...il.com, indan@....nu,
pmoore@...hat.com, akpm@...ux-foundation.org, corbet@....net,
eric.dumazet@...il.com, keescook@...omium.org
Subject: Re: [PATCH v8 5/8] seccomp: Add SECCOMP_RET_TRAP
On 02/16/2012 12:28 PM, Markus Gutschke wrote:
> On Thu, Feb 16, 2012 at 12:02, Will Drewry <wad@...omium.org> wrote:
>> Adds a new return value to seccomp filters that triggers a SIGTRAP to be delivered with the new TRAP_SECCOMP si_code.
>>
>> This allows in-process system call emulation -- including just specifying an errno or cleanly dumping core -- rather than just dying.
>
> SIGTRAP might not be the ideal choice of signal number, as it can make
> it very difficult to debug the program in gdb. Other than that, I love
> this feature. It'll significantly simplify the code that we have in
> Chrome.
>
Sounds like SIGSYS to me.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
--
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