From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] heads up: 2.4.18 bug causing bad value in siginfo.si_fd
Date: Tue, 27 Aug 2002 18:15:54 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905986@msgid-missing> (raw)
It has been brought to my attention that there is a bug in the ia64
version of 2.4.18 which causes a bad value to be returned in the si_fd
member of the siginfo structure. This bug occurs at least for siginfo
values returned by sigtimedwait(), but I suspect the root cause is in
the siginfo-copying routines so normal signal deliver probably also
results in a bad si_fd value.
The bug is not present in 2.4.19 and 2.5.31.
--david
reply other threads:[~2002-08-27 18:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=marc-linux-ia64-105590701905986@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@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