From: Daniel Jacobowitz <dan@debian.org>
To: "Vamsi Krishna S ." <vamsi@in.ibm.com>
Cc: Mark Gross <mgross@unix-os.sc.intel.com>,
Pavel Machek <pavel@suse.cz>,
linux-kernel@vger.kernel.org, alan@lxorguk.ukuu.org.uk,
marcelo@conectiva.com.br, tachino@jp.fujitsu.com,
jefreyr@pacbell.net, vamsi_krishna@in.ibm.com,
richardj_moore@uk.ibm.com, hanharat@us.ibm.com,
bsuparna@in.ibm.com, bharata@in.ibm.com,
asit.k.mallick@intel.com, david.p.howell@intel.com,
tony.luck@intel.com, sunil.saxena@intel.com
Subject: Re: [PATCH] multithreaded coredumps for elf exeecutables
Date: Thu, 21 Mar 2002 11:27:22 -0500 [thread overview]
Message-ID: <20020321112722.A31634@nevyn.them.org> (raw)
In-Reply-To: <20020315170726.A3405@in.ibm.com> <20020319152959.C55@toy.ucw.cz> <200203192147.g2JLl3W01070@unix-os.sc.intel.com> <20020320113630.A6882@in.ibm.com> <20020320133709.A10958@nevyn.them.org> <20020321154650.A1435@in.ibm.com>
On Thu, Mar 21, 2002 at 03:46:50PM +0530, Vamsi Krishna S . wrote:
> Dan,
>
> Thanks for pointing this out. I see that this change has now gone into
> 2.4.18 as well as 2.5.4. We would ensure that the down_write happens
> only after the registers of all threads are collected.
Yes, your other patch for this looks OK.
> Coming back to the original point raised by Pavel, indeed there is
> nothing preventing external code (any other kernel modules) modifying
> the cpus_allowed field from under us. This could get worse in 2.5.x
> where a user could change cpu affinity (through proc or a syscall,
> though I don't think the patches providing this are accepted as yet).
We really need a non-signal-based way to tell the scheduler that a task
can not be scheduled. A lot of the machinery is all there, but private to
sched.c; the rest is pretty straightforward.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-03-21 16:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-15 11:37 [PATCH] multithreaded coredumps for elf exeecutables Vamsi Krishna S .
2002-03-19 15:29 ` Pavel Machek
2002-03-19 18:49 ` Mark Gross
2002-03-20 6:06 ` Vamsi Krishna S .
2002-03-20 18:37 ` Daniel Jacobowitz
2002-03-20 16:14 ` Mark Gross
2002-03-21 10:03 ` Vamsi Krishna S .
2002-03-22 16:19 ` Mark Gross
2002-03-21 10:16 ` Vamsi Krishna S .
2002-03-21 16:27 ` Daniel Jacobowitz [this message]
2002-03-21 16:52 ` Alan Cox
2002-03-21 14:10 ` Mark Gross
2002-03-21 17:34 ` Alan Cox
2002-03-21 14:59 ` Mark Gross
2002-03-21 20:25 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2002-03-22 6:06 Suparna Bhattacharya
2002-03-29 5:43 ` Jeff Jenkins
2002-03-29 12:50 ` Mark Gross
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=20020321112722.A31634@nevyn.them.org \
--to=dan@debian.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=asit.k.mallick@intel.com \
--cc=bharata@in.ibm.com \
--cc=bsuparna@in.ibm.com \
--cc=david.p.howell@intel.com \
--cc=hanharat@us.ibm.com \
--cc=jefreyr@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=mgross@unix-os.sc.intel.com \
--cc=pavel@suse.cz \
--cc=richardj_moore@uk.ibm.com \
--cc=sunil.saxena@intel.com \
--cc=tachino@jp.fujitsu.com \
--cc=tony.luck@intel.com \
--cc=vamsi@in.ibm.com \
--cc=vamsi_krishna@in.ibm.com \
/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.