[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20180216.162248.2136274977153072425.davem@davemloft.net>
Date: Fri, 16 Feb 2018 16:22:48 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: dhowells@...hat.com
Cc: netdev@...r.kernel.org, linux-afs@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH net] rxrpc: Work around usercopy check
From: David Howells <dhowells@...hat.com>
Date: Thu, 15 Feb 2018 22:59:00 +0000
> Due to a check recently added to copy_to_user(), it's now not permitted to
> copy from slab-held data to userspace unless the slab is whitelisted. This
> affects rxrpc_recvmsg() when it attempts to place an RXRPC_USER_CALL_ID
> control message in the userspace control message buffer. A warning is
> generated by usercopy_warn() because the source is the copy of the
> user_call_ID retained in the rxrpc_call struct.
>
> Work around the issue by copying the user_call_ID to a variable on the
> stack and passing that to put_cmsg().
>
> The warning generated looks like:
...
> Reported-by: Jonathan Billings <jsbillings@...illings.org>
> Signed-off-by: David Howells <dhowells@...hat.com>
> Acked-by: Kees Cook <keescook@...omium.org>
> Tested-by: Jonathan Billings <jsbillings@...illings.org>
Applied, thanks David.
Powered by blists - more mailing lists