[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230811-overture-catnip-2b004303cbc5@wendy>
Date: Fri, 11 Aug 2023 12:54:26 +0100
From: Conor Dooley <conor.dooley@...rochip.com>
To: Alexandre Ghiti <alex@...ti.fr>
CC: Alexandre Ghiti <alexghiti@...osinc.com>,
Paul Walmsley <paul.walmsley@...ive.com>,
Palmer Dabbelt <palmer@...belt.com>,
Albert Ou <aou@...s.berkeley.edu>,
Alan Kao <alankao@...estech.com>,
<linux-riscv@...ts.infradead.org>, <linux-kernel@...r.kernel.org>,
Bo YU <tsu.yubo@...il.com>,
Aurelien Jarno <aurelien@...el32.net>
Subject: Re: [PATCH -fixes] riscv: uaccess: Return the number of bytes
effectively copied
On Fri, Aug 11, 2023 at 01:39:16PM +0200, Alexandre Ghiti wrote:
> On 11/08/2023 13:03, Alexandre Ghiti wrote:
> > It was reported that the riscv kernel hangs while executing the test
> > in [1].
> >
> > Indeed, the test hangs when trying to write a buffer to a file. The
> > problem is that the riscv implementation of raw_copy_from_user() does not
> > return the number of bytes written when an exception happens and is fixed
> > up.
>
>
> I'll respin another version as the changelog and the title are incorrect:
> the uaccess routines should not return the number of bytes copied but
> actually the number of bytes not copied (this is what this patch
> implements).
>
> I'll wait for feedbacks before doing so!
While you're editing te changelog, can you make the link a regular Link:
tag? You can do `Link: <foo> [1]`.
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists