[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <855df2ca-0760-2106-4e3b-2af7ce15b9eb@infradead.org>
Date: Fri, 30 Dec 2022 12:22:50 -0800
From: Randy Dunlap <rdunlap@...radead.org>
To: Federico Vaga <federico.vaga@...a.pv.it>,
Jonathan Corbet <corbet@....net>
Cc: linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH V2] doc: fix typo in botching up ioctls
On 12/30/22 09:23, Federico Vaga wrote:
> The type contained a typo `uintprt` -> `uintptr`
>
> Signed-off-by: Federico Vaga <federico.vaga@...a.pv.it>
Acked-by: Randy Dunlap <rdunlap@...radead.org>
Thanks.
> ---
> Documentation/process/botching-up-ioctls.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> v1 -> v2 fix the typo in the commit message
>
> diff --git a/Documentation/process/botching-up-ioctls.rst b/Documentation/process/botching-up-ioctls.rst
> index ba4667ab396b..9739b88463a5 100644
> --- a/Documentation/process/botching-up-ioctls.rst
> +++ b/Documentation/process/botching-up-ioctls.rst
> @@ -41,7 +41,7 @@ will need to add a 32-bit compat layer:
> structures to the kernel, or if the kernel checks the structure size, which
> e.g. the drm core does.
>
> - * Pointers are __u64, cast from/to a uintprt_t on the userspace side and
> + * Pointers are __u64, cast from/to a uintptr_t on the userspace side and
> from/to a void __user * in the kernel. Try really hard not to delay this
> conversion or worse, fiddle the raw __u64 through your code since that
> diminishes the checking tools like sparse can provide. The macro
--
~Randy
Powered by blists - more mailing lists