From: Jakub Jelinek <jakub@redhat.com>
To: Andi Kleen <ak@suse.de>
Cc: Joe Korty <joe.korty@ccur.com>,
akpm@osdl.org, torvalds@osdl.org, linux-kernel@vger.kernel.org,
albert.cahalan@ccur.com, jim.houston@ccur.com
Subject: Re: siginfo_t fracturing, especially for 64/32-bit compatibility mode
Date: Fri, 2 Jan 2004 19:44:06 -0500 [thread overview]
Message-ID: <20040103004406.GA24876@devserv.devel.redhat.com> (raw)
In-Reply-To: <20040103012433.6aa4cafb.ak@suse.de>
On Sat, Jan 03, 2004 at 01:24:33AM +0100, Andi Kleen wrote:
> > rt_sigqueueinfo(2) subverts this by reserving a range of si_code
> > values for users, and there is nothing about them to indicate to the
> > kernel which fields of siginfo_t are actually in use. This is not a
>
> My understanding was that the syscall always only supports si_int/si_ptr.
No, why?
> >
> > The current conflicts are:
>
> [...SI_TKILL, SI_ASYNCIO...] that's broken. We just cannot support that. This aspect of
> SuS just cannot be emulated in user space, glibc was misguided about attempting
> it.
SI_ASYNCNL is -60, not -6.
Negative si_code values are reserved for userspace, while positive ones are for
kernel space.
Jakub
next prev parent reply other threads:[~2004-01-03 0:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-02 19:49 Joe Korty
2004-01-02 20:28 ` Linus Torvalds
2004-01-02 20:38 ` Joe Korty
2004-01-02 20:47 ` Linus Torvalds
2004-03-29 15:39 ` Linus Torvalds
2004-03-29 15:39 ` Joe Korty
2004-01-03 0:24 ` Andi Kleen
2004-01-03 0:44 ` Jakub Jelinek [this message]
2004-01-03 1:07 ` Andi Kleen
2004-01-03 2:12 ` Daniel Jacobowitz
2004-03-29 15:39 ` Daniel Jacobowitz
2004-03-29 15:39 ` Andi Kleen
2004-01-03 20:15 ` Joe Korty
2004-03-29 15:39 ` Jakub Jelinek
2004-03-29 15:40 ` Joe Korty
2004-03-29 15:39 ` Linus Torvalds
2004-03-29 15:39 ` Andi Kleen
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=20040103004406.GA24876@devserv.devel.redhat.com \
--to=jakub@redhat.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=albert.cahalan@ccur.com \
--cc=jim.houston@ccur.com \
--cc=joe.korty@ccur.com \
--cc=linux-kernel@vger.kernel.org \
--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
Powered by JetHome