Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
IronPort-SDR: sl0pWYsrzo1WizLcFQJCThEl3psYdQ5qorW4DLQAOpQyWenFwIWU83U6DbJm0HeWzMy7GYV4SN
 KQxFlhLHfB1qVrZDRUxMCqZbI9Mze58YSbkuj8IVCRMSkoYC/1C00Y44wkE0DecfdvH96vS5RR
 LsbGHDwMl1nT3KLISr92GHGBGJutJWCrLkcJtj3k2Fn/BKmowWRUs8X01iwYiLwW97daOJ38gd
 il9StJWX5IZbmszeCqheihOeRz51Yxe2ZbJGJDTRFMLvk/qud4H0cSLihbQvBnre2WOAeDNtjN
 Hbw=
IronPort-SDR: Cv0UqDRPdqm7tL2awNL5BBMz4ALeO/qghQctSObPmRAsyxKJVO8QKz3aA8W+xo3o/vWMT62emF
 bM8ofbCrY1HjilujaKmvpBnwkmIR6+MSE4/c+hZ42TWZ9OhGHYBKCJwa7MpmPjqrkyGmxtNfIC
 N33UIPRKqtKn9BQNWz5nSiFc/RkWmB7ZdxMjVwwq9H4snENgVNz9O8Ql5trNREuO2+lnlVcjQ6
 bGwBISNPnyefffkhXh/Bdt5Lw8cK0iZ9bxgC4RwOhT9pfzNhdEaMcfb7CyEPYZjK6uax4BcmCK
 7ziMww4848sHmLeJZCagan9/
IronPort-SDR: 3uwdGreIxlVjC6rLHAVUNPxCvYFm12JW++t5byZuYThYEKpHQy1rvPmQ3xRuq3bHiMuNnv4Hq7
 63wzCLqFIFApUyBBAcjPM74IesbGPjKYsPFPpuufziviVGB/UkXWgcGM2tZsqTjMkIhvf4D+UQ
 QojHazb4wUUMSjboC3ARtuE89wBtlKhK6Jx8R0Q4qcn4UNQJe3cHoKaHzdb/G2Cyi68fnwbElo
 tp+WtZHcEEzeowOCXxYJUduMa2yzOo5GB0CBsspNsy7AprVueWfrW2IeIt7UG4W4ouF7OhCsgw
 AVk=
From:   Alistair Francis <alistair.francis@wdc.com>
To:     linux-riscv@lists.infradead.org, arnd@arndb.de
Cc:     linux-kernel@vger.kernel.org, alistair23@gmail.com,
        Alistair Francis <alistair.francis@wdc.com>
Subject: [PATCH RESEND 0/2] RISC-V: Handle the siginfo_t offset problem
Date:   Tue,  2 Jul 2019 17:52:00 -0700
Message-Id: <20190703005202.7578-1-alistair.francis@wdc.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Resending the the correct linux-riscv address.

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