Linux-Next discussions
 help / color / mirror / Atom feed
From: Josh Poimboeuf <jpoimboe@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Jens Axboe <axboe@kernel.dk>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of the block tree
Date: Wed, 12 Apr 2023 09:25:17 -0700	[thread overview]
Message-ID: <20230412162517.gji52t34zlvcu5bh@treble> (raw)
In-Reply-To: <20230412114400.GB628377@hirez.programming.kicks-ass.net>

On Wed, Apr 12, 2023 at 01:44:00PM +0200, Peter Zijlstra wrote:
> On Tue, Apr 11, 2023 at 05:14:00PM -0700, Josh Poimboeuf wrote:
> 
> > Peter, what do you think, should we make track uaccess state across
> > function boundaries?
> 
> So IIRC the goal was to explicitly dis-allow that. You want minimal code
> executed with STAC and hence disallow calling stuff.

I guess I was wondering if we could make an exception for calls to
static IPA-optimized functions, so we wouldn't have to scramble to "fix"
compiler optimizations.

But for now, yeah let's just keep it simple.

Jens, can you confirm this works?  I added __noclone instead of removing
static.

---8<---

From: Josh Poimboeuf <jpoimboe@kernel.org>
Subject: [PATCH] iov_iter: Mark copy_compat_iovec_from_user() noinline

After commit 6376ce56feb6 ("iov_iter: import single vector iovecs as
ITER_UBUF"), GCC does an inter-procedural compiler optimization which
moves the user_access_begin() out of copy_compat_iovec_from_user() and
into its callers:

  lib/iov_iter.o: warning: objtool: .altinstr_replacement+0x0: redundant UACCESS disable
  lib/iov_iter.o: warning: objtool: iovec_from_user.part.0+0xc7: call to copy_compat_iovec_from_user.part.0() with UACCESS enabled
  lib/iov_iter.o: warning: objtool: __import_iovec+0x21d: call to copy_compat_iovec_from_user.part.0() with UACCESS enabled

Enforce the "no UACCESS enable across function boundaries" rule by
disabling cloning for copy_compat_iovec_from_user().

Fixes: 6376ce56feb6 ("iov_iter: import single vector iovecs as ITER_UBUF")
Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
https://lkml.kernel.org/lkml/20230327120017.6bb826d7@canb.auug.org.au
Signed-off-by: Josh Poimboeuf <jpoimboe@kernel.org>
---
 lib/iov_iter.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/iov_iter.c b/lib/iov_iter.c
index 274014e4eafe..48aa9fd99267 100644
--- a/lib/iov_iter.c
+++ b/lib/iov_iter.c
@@ -1698,7 +1698,7 @@ const void *dup_iter(struct iov_iter *new, struct iov_iter *old, gfp_t flags)
 }
 EXPORT_SYMBOL(dup_iter);
 
-static int copy_compat_iovec_from_user(struct iovec *iov,
+static __noclone int copy_compat_iovec_from_user(struct iovec *iov,
 		const struct iovec __user *uvec, unsigned long nr_segs)
 {
 	const struct compat_iovec __user *uiov =
-- 
2.39.2


  reply	other threads:[~2023-04-12 16:25 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-27  1:00 linux-next: build warnings after merge of the block tree Stephen Rothwell
2023-03-27 16:26 ` Josh Poimboeuf
2023-03-27 23:47   ` Stephen Rothwell
2023-04-11 21:34     ` Stephen Rothwell
2023-04-11 21:55       ` Josh Poimboeuf
2023-04-11 22:39         ` Jens Axboe
2023-04-12  0:14           ` Josh Poimboeuf
2023-04-12  1:48             ` Jens Axboe
2023-04-12 11:44             ` Peter Zijlstra
2023-04-12 16:25               ` Josh Poimboeuf [this message]
2023-04-12 16:35                 ` Jens Axboe
2023-04-12 16:44                   ` Jens Axboe
2023-04-12 16:56                     ` Josh Poimboeuf
2023-04-12 17:57                       ` Jens Axboe
2023-06-16 12:43                 ` Peter Zijlstra
2023-06-16 12:49                   ` Borislav Petkov
2023-07-03 11:04                   ` Peter Zijlstra
2023-07-03 14:18                     ` Jens Axboe
2023-07-03 15:14                       ` Peter Zijlstra
2023-04-11 22:30       ` Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2024-09-16  8:36 Stephen Rothwell
2024-09-16  8:49 ` Keith Busch
2024-09-27  3:43 ` Stephen Rothwell
2024-09-27 10:20   ` Jens Axboe
2024-10-03  3:18     ` Stephen Rothwell
2024-10-03 12:31       ` Jens Axboe
2024-02-06  2:10 Stephen Rothwell
2024-02-06  4:13 ` Stephen Rothwell
2024-02-06 11:12 ` Geert Uytterhoeven
2024-02-06 13:42   ` Geert Uytterhoeven
2024-02-06 14:53     ` Jens Axboe
2024-02-06 14:49 ` Jens Axboe
2023-07-27  6:10 Stephen Rothwell
2023-07-27 12:41 ` Jens Axboe
2022-07-15 11:51 Stephen Rothwell
2020-03-03  1:41 Stephen Rothwell
2020-03-03  2:59 ` Jens Axboe
2018-03-01  0:26 Stephen Rothwell
2018-03-01  4:02 ` Anshuman Khandual
2018-03-01 15:37   ` Jens Axboe
2013-11-26  2:29 Stephen Rothwell
2013-11-26  3:35 ` Stephen Rothwell
2013-11-26 19:01   ` Olof Johansson
2013-11-26 19:02     ` Jens Axboe
2011-01-07  0:02 Stephen Rothwell
2011-01-07  1:49 ` Mathieu Desnoyers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230412162517.gji52t34zlvcu5bh@treble \
    --to=jpoimboe@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox