From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch 2.6.10-rc3] Add TIF_SIGDELAYED processing
Date: Thu, 09 Dec 2004 23:08:35 +0000 [thread overview]
Message-ID: <16824.56051.207249.1262@napali.hpl.hp.com> (raw)
In-Reply-To: <15449.1102482344@kao1.melbourne.sgi.com>
>>>>> On Thu, 09 Dec 2004 12:41:33 +1100, Keith Owens <kaos@sgi.com> said:
>> It seems rather dangerous to stash away PIDs and deliver signals
>> to them later on. It's just an invitation for races, IMHO.
Keith> The pid is checked to see if it is still valid, see
Keith> do_sigdelayed(). Yes, there is a very small race where the
Keith> pid could be reused, but to hit that race we have to -
I just think stashing away pids in the kernel is a slippery slope we
do not want to get onto.
Can't you stash away a reference to the task-structure and bump the
reference count? I suspect that might get you into trouble when a
task exits with first unmapping all MMIO-memory, but that's might not
be so hard to deal with (when task exits, check whether it has any
MMIO mappings and if so, kill those, or at least the associated
registrations first).
--david
next prev parent reply other threads:[~2004-12-09 23:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-08 5:05 [patch 2.6.10-rc3] Add TIF_SIGDELAYED processing Keith Owens
2004-12-08 17:11 ` Luck, Tony
2004-12-09 1:10 ` Keith Owens
2004-12-09 1:22 ` David Mosberger
2004-12-09 1:41 ` Keith Owens
2004-12-09 23:08 ` David Mosberger [this message]
2004-12-09 23:19 ` Luck, Tony
2004-12-09 23:22 ` David Mosberger
2004-12-10 0:28 ` Jesse Barnes
2004-12-10 1:21 ` Keith Owens
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=16824.56051.207249.1262@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox