From: Daniel Jacobowitz <dan@debian.org>
To: "Davda, Bhavesh P (Bhavesh)" <bhavesh@avaya.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] New SA_NOPRNOTIF sigaction flag
Date: Sun, 2 Oct 2005 20:27:16 -0400 [thread overview]
Message-ID: <20051003002716.GA5726@nevyn.them.org> (raw)
In-Reply-To: <21FFE0795C0F654FAD783094A9AE1DFC086F0379@cof110avexu4.global.avaya.com>
On Wed, Sep 28, 2005 at 01:11:22PM -0600, Davda, Bhavesh P (Bhavesh) wrote:
> How about 2 new PTRACE requests: PTRACE_SET_SIGIGN_MASK,
> PTRACE_GET_SIGIGN_MASK
>
> Both taking a "sigset_t *mask" as a parameter? The mask would be filled
> by the debugger as usual using sigemptyset(), sigfillset(), sigaddset(),
> etc.
>
> Of course, the implementation would do error checking for legal values
> of signals to mask, etc.
>
> And this might require augmenting task_struct {} to store this mask,
> kind of like last_siginfo which is already used by the
> PTRACE_SETSIGINFO/PTRACE_GETSIGINFO ptrace requests.
Hmm, the only problem with this is that it requires consensus on the
format of kernel sigsets. Think about the 32-vs-64-bit compatibility
issues.
It should be cleared on PTRACE_DETACH, of course. Do we even need the
GET functionality? If not, is PTRACE_SET_IGNORE_SIGNAL taking a single
signal number sufficient?
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-10-03 0:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-28 19:11 [RFC PATCH] New SA_NOPRNOTIF sigaction flag Davda, Bhavesh P (Bhavesh)
2005-10-03 0:27 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-03 15:21 Davda, Bhavesh P (Bhavesh)
2005-10-03 16:12 ` Daniel Jacobowitz
2005-09-28 18:06 Davda, Bhavesh P (Bhavesh)
2005-09-28 18:33 ` Daniel Jacobowitz
2005-09-27 21:55 Davda, Bhavesh P (Bhavesh)
2005-09-28 14:10 ` Daniel Jacobowitz
2005-09-27 16:24 Davda, Bhavesh P (Bhavesh)
2005-09-27 20:39 ` Daniel Jacobowitz
2005-09-27 14:45 Davda, Bhavesh P (Bhavesh)
2005-09-27 15:55 ` Daniel Jacobowitz
2005-09-27 23:26 ` Valdis.Kletnieks
2005-09-26 17:39 Bhavesh P. Davda
2005-09-27 13:06 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051003002716.GA5726@nevyn.them.org \
--to=dan@debian.org \
--cc=bhavesh@avaya.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.