From: Alistair Francis <alistair.francis@wdc.com>
To: linux-riscv-bounces@lists.infradead.org, arnd@arndb.de
Cc: linux-kernel@vger.kernel.org, alistair23@gmail.com,
Alistair Francis <alistair.francis@wdc.com>
Subject: [PATCH 0/2] RISC-V: Handle the siginfo_t offset problem
Date: Tue, 2 Jul 2019 17:18:40 -0700 [thread overview]
Message-ID: <20190703001842.12238-1-alistair.francis@wdc.com> (raw)
In the RISC-V 32-bit glibc port [1] the siginfo_t struct in the kernel
doesn't line up with the struct in glibc. In glibc world the _sifields
union is 8 byte alligned (although I can't figure out why) while in the
kernel wordl the _sifields union is 4 bytes alligned. This results in
information being lost in the waitid syscall.
This doesn't seem to be a great fix, but it is somewhat similar to what
x32 does (which has 64-bit time_t like RV32) and I can't figure out why
the two allignments are different.
1: https://github.com/alistair23/glibc/commits/alistair/rv32.next
Alistair Francis (2):
uapi/asm-generic: Allow defining a custom __SIGINFO struct
riscv/include/uapi: Define a custom __SIGINFO struct for RV32
arch/riscv/include/uapi/asm/siginfo.h | 32 +++++++++++++++++++++++++++
include/uapi/asm-generic/siginfo.h | 32 ++++++++++++++-------------
2 files changed, 49 insertions(+), 15 deletions(-)
create mode 100644 arch/riscv/include/uapi/asm/siginfo.h
--
2.22.0
next reply other threads:[~2019-07-03 0:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-03 0:18 Alistair Francis [this message]
2019-07-03 0:18 ` [PATCH 1/2] uapi/asm-generic: Allow defining a custom __SIGINFO struct Alistair Francis
2019-07-03 8:31 ` Arnd Bergmann
2019-07-03 0:18 ` [PATCH 2/2] riscv/include/uapi: Define a custom __SIGINFO struct for RV32 Alistair Francis
2019-07-03 8:40 ` Arnd Bergmann
2019-07-03 18:42 ` Alistair Francis
2019-07-03 19:47 ` Arnd Bergmann
2019-07-03 22:15 ` Alistair Francis
2019-07-04 8:34 ` Arnd Bergmann
2019-07-09 22:55 ` Alistair Francis
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=20190703001842.12238-1-alistair.francis@wdc.com \
--to=alistair.francis@wdc.com \
--cc=alistair23@gmail.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv-bounces@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).