public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dan@debian.org>
To: Albert Cahalan <albert@users.sf.net>
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: CLONE_SIGHAND w/o CLONE_VM
Date: Sun, 21 Sep 2003 23:41:46 -0400	[thread overview]
Message-ID: <20030922034146.GA8083@nevyn.them.org> (raw)
In-Reply-To: <1064199244.746.401.camel@cube>

On Sun, Sep 21, 2003 at 10:54:05PM -0400, Albert Cahalan wrote:
> Does CLONE_SIGHAND without CLONE_VM ever
> make sense?
> 
> Note that the arch-specific kernel_thread()
> implementations add CLONE_VM, so kernel_thread()
> usage doesn't count unless you can point to an
> arch that doesn't add the CLONE_VM flag. (BTW, the
> user-mode port is missing CLONE_UNTRACED. Bug?)

Minor bug, but yes, it's a bug.  kernel threads should always be
CLONE_UNTRACED; UML wasn't in the tree when I added it.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

      reply	other threads:[~2003-09-22  3:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-22  2:54 CLONE_SIGHAND w/o CLONE_VM Albert Cahalan
2003-09-22  3:41 ` Daniel Jacobowitz [this message]

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=20030922034146.GA8083@nevyn.them.org \
    --to=dan@debian.org \
    --cc=albert@users.sf.net \
    --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