From: "J.A. Magallon" <jamagallon@able.es>
To: Christoph Hellwig <hch@infradead.org>
Cc: Lista Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: __NR_exit_group for 2.4-O(1)
Date: Fri, 3 Jan 2003 01:50:33 +0100 [thread overview]
Message-ID: <20030103005033.GA3103@werewolf.able.es> (raw)
In-Reply-To: <20030103004557.A10881@infradead.org>; from hch@infradead.org on Fri, Jan 03, 2003 at 01:45:57 +0100
On 2003.01.03 Christoph Hellwig wrote:
> On Fri, Jan 03, 2003 at 01:36:17AM +0100, J.A. Magallon wrote:
> > > Your libc isn't the one from RH's new beta, is it? :)
> > >
> >
> > Nope, Mandrake Cooker glibc-2.3.1-6.
>
> glibc only tries to use sys_exit_group if the kernel headers it's compiled
> against define __NR_exit_group. AFAIK only the current RH beta ships
> a kernel with a 2.4 backport of all the threading changes during 2.5, so
> it might be worth asking the mdk glibc maintainer we he got his kernel
> headers from.. (either redhat or 2.5 :))
>
It is defined in 2.4.20, undefined but reserved:
werewolf:/usr/src/linux-2.4.20> grep -r exit_group *
arch/x86_64/ia32/ia32entry.S: .quad sys_ni_syscall /* exit_group */
arch/i386/kernel/entry.S: .long SYMBOL_NAME(sys_ni_syscall) /* sys_exit_group */
include/asm-x86_64/ia32_unistd.h:#define __NR_ia32_exit_group 252
include/asm-i386/unistd.h:#define __NR_exit_group 252
???
--
J.A. Magallon <jamagallon@able.es> \ Software is like sex:
werewolf.able.es \ It's better when it's free
Mandrake Linux release 9.1 (Cooker) for i586
Linux 2.4.21-pre2-jam2 (gcc 3.2.1 (Mandrake Linux 9.1 3.2.1-2mdk))
next prev parent reply other threads:[~2003-01-03 0:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-03 0:15 __NR_exit_group for 2.4-O(1) J.A. Magallon
2003-01-03 0:22 ` William Lee Irwin III
2003-01-03 0:32 ` Christoph Hellwig
2003-01-03 0:36 ` J.A. Magallon
2003-01-03 0:45 ` Christoph Hellwig
2003-01-03 0:50 ` J.A. Magallon [this message]
2003-01-03 0:56 ` Christoph Hellwig
2003-01-03 3:23 ` Ulrich Drepper
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=20030103005033.GA3103@werewolf.able.es \
--to=jamagallon@able.es \
--cc=hch@infradead.org \
--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