Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
IronPort-SDR: cAQl5o5vxYIbbHmq0jCHSomOpbLo7MT+cfuc89UXcL/neg0X/nvAnexHLpYYCfx5vcLsCcxDIF
 Pe3bbOh8kpMbkmULar13NWADXSPNKmmzFpUNXQvZDrTSRrh7pCsbcL5l1klOyCkPs1JcgpRHlF
 mazRQXUxnAkRK2NznO9EWfh1nvdaVCNrrhQq7XCrjPdnK+3JjNMx+//7S1K0U9UhJdakO9I60j
 hooouX+Htp05eRscN9Icwwvg7erMXWPmFpxTaJL0rkFHES4FvkV8eUCRKK9mQsdDmjUI2S/Nnq
 jx4=
IronPort-SDR: A685du3fDRLzqCOVDoE/3cKvvNi/bs23ylvn9j/socAgIab+OXhm7n8QA0YtSpv7zv4MEyGsCr
 1WGBf6a970zH1hbDoW/s2C4Puepu7Z3no=
IronPort-SDR: ZPvGnB3aMrvnPWiKC7eRCLgc2ktzcPW7hTaG4A1gddAOuTb3tpozRaADX96nfFxia79ARXWeH9
 j6d7hGRNqG/w==
WDCIronportException: Internal
Date:   Fri, 24 Jul 2020 00:21:57 +0100 (BST)
From:   "Maciej W. Rozycki" <macro@wdc.com>
To:     linux-riscv@lists.infradead.org
cc:     Paul Walmsley <paul.walmsley@sifive.com>,
        Palmer Dabbelt <palmer@dabbelt.com>,
        Albert Ou <aou@eecs.berkeley.edu>, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] riscv: ptrace: NT_PRFPREG regset access fixes
Message-ID: <alpine.LFD.2.21.2007232038170.24175@redsun52.ssa.fujisawa.hgst.com>
User-Agent: Alpine 2.21 (LFD 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Hi,

 In the course of adding RISC-V/Linux support to `gdbserver' I examined 
our Linux regset code to make sure I get the userland side right and 
discovered a discrepancy between how our internal `user_regset_copyout' 
and `user_regset_copyout' API has been defined and how we call it in the 
RISC-V backend in the handling of the NT_PRFPREG regset.  Additionally I 
found that code violating our coding style.

 To address these issues I made this small patch set, addressing each of 
them separately.  See individual change descriptions for details.

 These changes are hopefully obviously correct, however to make sure I 
have verified them manually with a HiFive Unleashed board running 
`gdbserver' controlled remotely by GDB and also by running the full GDB 
testsuite in the same environment using the lp64d ABI, without and with 
the changes applied.

 Please apply.

  Maciej