From: Jamie Lokier <jamie@shareable.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Roland McGrath <roland@redhat.com>, Andrew Morton <akpm@osdl.org>,
Matt Wilson <msw@redhat.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: [PATCH] revert zap_other_threads breakage, disallow CLONE_THREAD without CLONE_DETACHED
Date: Thu, 14 Aug 2003 19:27:57 +0100 [thread overview]
Message-ID: <20030814182757.GA11623@mail.jlokier.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0308141101110.1692-100000@home.osdl.org>
Linus Torvalds wrote:
> > Don't forget to mention that software that may be run on 2.5 kernels
> > needs to set both bits, else won't work as expected.
>
> Well, the CLONE_DETACHED without CLONE_THREAD case was never legal, and my
> current patch will actually warn about the newly disallowed case too. I've
> not gotten any warnings with RH-9, and I don't think anybody else has a
> new enough glibc to even use CLONE_THREAD at all.
I'm thinking of programs that don't use Glibc, but do use these features.
Perhaps I'm the only person who writes such code :)
> But yes, there will be a warning, at least for a time (and eventually
> we'll just return -EINVAL silently - ie the program will _fail_ the
> clone(), it won't just act strangely).
-EINVAL would be great.
-- Jamie
next prev parent reply other threads:[~2003-08-14 18:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-09 19:17 [PATCH] zap_other_threads() detaches thread group leader Matt Wilson
2003-08-12 7:40 ` Roland McGrath
2003-08-12 7:52 ` [PATCH] revert zap_other_threads breakage, disallow CLONE_THREAD without CLONE_DETACHED Roland McGrath
2003-08-13 7:11 ` Jeremy Fitzhardinge
2003-08-13 9:37 ` Roland McGrath
2003-08-14 17:32 ` Linus Torvalds
2003-08-14 17:53 ` Jamie Lokier
2003-08-14 18:03 ` Linus Torvalds
2003-08-14 18:27 ` Jamie Lokier [this message]
2003-08-14 18:33 ` Linus Torvalds
2003-08-14 18:38 ` Jamie Lokier
2003-08-14 20:56 ` Roland McGrath
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=20030814182757.GA11623@mail.jlokier.co.uk \
--to=jamie@shareable.org \
--cc=akpm@osdl.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=msw@redhat.com \
--cc=roland@redhat.com \
--cc=torvalds@osdl.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®