Subject: Re: linux-next: build warnings after merge of the block tree

From: Peter Zijlstra <[email-masked]>
Date: Mon, 3 Jul 2023 13:04:05 +0200

On Fri, Jun 16, 2023 at 02:43:55PM +0200, Peter Zijlstra wrote:

> I've been getting reports from some anonymous people still using ancient
> GCCs (10.4) that also need the following:

Jens, will you pick this up or should I route it through the objtool
tree?

> ---
> Subject: iov_iter: Mark copy_iovec_from_user() noclone
> 
> Extend commit 50f9a76ef127 ("iov_iter: Mark
> copy_compat_iovec_from_user() noinline") to also cover
> copy_iovec_from_user(). Different compiler versions cause the same
> problem on different functions.
> 
> lib/iov_iter.o: warning: objtool: .altinstr_replacement+0x1f: redundant UACCESS disable
> lib/iov_iter.o: warning: objtool: iovec_from_user+0x84: call to copy_iovec_from_user.part.0() with UACCESS enabled
> lib/iov_iter.o: warning: objtool: __import_iovec+0x143: call to copy_iovec_from_user.part.0() with UACCESS enabled
> 
> Fixes: 50f9a76ef127 ("iov_iter: Mark copy_compat_iovec_from_user() noinline")
> Signed-off-by: Peter Zijlstra (Intel) <[email-masked]>
> ---
> diff --git a/lib/iov_iter.c b/lib/iov_iter.c
> index 960223ed9199..061cc3ed58f5 100644
> --- a/lib/iov_iter.c
> +++ b/lib/iov_iter.c
> @@ -1795,7 +1795,7 @@ static __noclone int copy_compat_iovec_from_user(struct iovec *iov,
>  	return ret;
>  }
>  
> -static int copy_iovec_from_user(struct iovec *iov,
> +static __noclone int copy_iovec_from_user(struct iovec *iov,
>  		const struct iovec __user *uiov, unsigned long nr_segs)
>  {
>  	int ret = -EFAULT;