From: David Mosberger <davidm@hpl.hp.com>
To: Andrea Arcangeli <andrea@suse.de>
Cc: David Mosberger <davidm@hpl.hp.com>, linux-kernel@vger.kernel.org
Subject: Re: [patch] proposed fix for ptrace() SMP race
Date: Mon, 10 Sep 2001 10:20:49 -0700 [thread overview]
Message-ID: <15260.63089.955454.709358@napali.hpl.hp.com> (raw)
In-Reply-To: <20010908191108.B11329@athlon.random>
In-Reply-To: <200109062300.QAA27430@napali.hpl.hp.com> <20010907021900.L11329@athlon.random> <15256.6038.599811.557582@napali.hpl.hp.com> <20010907032801.N11329@athlon.random> <15256.22858.57091.769101@napali.hpl.hp.com> <20010907152858.O11329@athlon.random> <15256.59715.523045.796917@napali.hpl.hp.com> <20010908191108.B11329@athlon.random>
>>>>> On Sat, 8 Sep 2001 19:11:08 +0200, Andrea Arcangeli <andrea@suse.de> said:
Andrea> On Fri, Sep 07, 2001 at 08:35:31AM -0700, David Mosberger
Andrea> wrote:
>> Also, other signals will still wake up the task. Yes, it won't
>> get very far as do_signal() will notify the parent instead, but
>> still, the task will run and that could be enough to create some
>> race condition.
Andrea> this is the real issue, agreed.
Good.
Andrea> However still I don't like the cpus_allowed racy approch. I
Andrea> either prefer to force the deschedule with a new ptrace
Andrea> bitflag with new hooks in the scheduler or with a blocker
Andrea> (delayer) to the signals again with a new ptrace bitflag but
Andrea> in this case with hooks in the signal code. I think putting
Andrea> the hooks in the signal code is better.
Yes, though I don't really see how you could do this without any
change to the scheduler.
Andrea> BTW, checking this stuff I found two bugs, one is the check
Andrea> for cpus_allowed before calling reschedule_idle, such check
Andrea> has to be removed, then it also seems the signals seems to
Andrea> wakeup the task two times unless I've overlooked something.
Andrea> You may want to make a new patch at the light of those
Andrea> considerations otherwise I'll put this in my todo list once
Andrea> more important things are solved.
Why don't you keep it on your todo list. I too have a couple of other
things I need to finish first so it will be a while before I'd get to
this (not before November, I'd guess). But I'll keep it in mind as
well.
Thanks,
--david
next prev parent reply other threads:[~2001-09-10 17:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-06 23:00 David Mosberger
2001-09-07 0:19 ` Andrea Arcangeli
2001-09-07 0:40 ` David Mosberger
2001-09-07 1:28 ` Andrea Arcangeli
2001-09-07 1:41 ` Alan Cox
2001-09-07 13:34 ` Andrea Arcangeli
2001-09-07 5:21 ` David Mosberger
2001-09-07 13:28 ` Andrea Arcangeli
2001-09-07 15:35 ` David Mosberger
2001-09-08 17:11 ` Andrea Arcangeli
2001-09-10 17:20 ` David Mosberger [this message]
2001-09-10 17:54 Manfred Spraul
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=15260.63089.955454.709358@napali.hpl.hp.com \
--to=davidm@hpl.hp.com \
--cc=andrea@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®