linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Laight <David.Laight@ACULAB.COM>
To: 'Linus Torvalds' <torvalds@linux-foundation.org>,
	Borislav Petkov <bp@alien8.de>
Cc: Josh Poimboeuf <jpoimboe@kernel.org>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	"Kirill A. Shutemov" <kirill@shutemov.name>,
	"x86@kernel.org" <x86@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <peterz@infradead.org>,
	Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
	Waiman Long <longman@redhat.com>,
	"Dave Hansen" <dave.hansen@linux.intel.com>,
	Ingo Molnar <mingo@redhat.com>,
	"Michael Ellerman" <mpe@ellerman.id.au>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
	Mark Rutland <mark.rutland@arm.com>
Subject: RE: [PATCH] x86/uaccess: Avoid barrier_nospec() in copy_from_user()
Date: Thu, 24 Oct 2024 09:21:56 +0000	[thread overview]
Message-ID: <c40199a2a319440d89bfcc5c06ec4b3a@AcuMS.aculab.com> (raw)
In-Reply-To: <CAHk-=wjpE4hgOs0q7-jZ+=RsCD=YX9R=V3SCprzg0GOUQfCHNw@mail.gmail.com>

From: Linus Torvalds
> Sent: 23 October 2024 21:08
> 
> On Wed, 23 Oct 2024 at 12:17, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> > NOTE! This is obviously untested and I didn't check that it does the
> > cmp/sbb/or the right way around.
> 
> Well, it boots. The code generation (from strncpy_from_user()) seems ok:
> 
>       movabs $0x123456789abcdef,%rcx
>       cmp    %rsi,%rcx
>       sbb    %ecx,%ecx
>       or     %rsi,%rcx
> 
> where obviously that constant is the bogus pre-initialized value, not
> the actual runtime value.

Would it be better to make the 'bogus' constant one that makes
all accesses fail?
So you soon find out it any code doesn't get patched.

I also wonder how big the table of addresses to patch is.
If that gets into inlined functions it could be big.

OTOH having a real function that does access_ok(), clac and address
masking may not problem.

Especially if there is always a (PAGE sized) gap between the highest
user address and the lowest kernel address so the 'size' argument
to access_ok() can be ignored on the assumption that the accesses
are (reasonably) linear.

	David

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)

  parent reply	other threads:[~2024-10-24  9:22 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-12  4:09 [PATCH] x86/uaccess: Avoid barrier_nospec() in copy_from_user() Josh Poimboeuf
2024-10-12  8:48 ` Andrew Cooper
2024-10-12 14:09   ` Josh Poimboeuf
2024-10-12 14:21     ` Borislav Petkov
2024-10-12 15:58       ` Linus Torvalds
2024-10-12 14:26     ` Andrew Cooper
2024-10-12 15:44   ` Linus Torvalds
2024-10-12 17:23     ` Andrew Cooper
2024-10-12 17:44       ` Linus Torvalds
2024-10-13  0:53         ` Linus Torvalds
2024-10-13  1:21           ` Linus Torvalds
2024-10-14  3:54             ` Josh Poimboeuf
2024-10-14  6:50               ` Linus Torvalds
2024-10-14  9:59                 ` David Laight
2024-10-14 11:20                   ` Linus Torvalds
2024-10-14 14:40                     ` David Laight
2024-10-14 11:12                 ` Andrew Cooper
2024-10-14 12:30                 ` Kirill A. Shutemov
2024-10-14 15:39                   ` Andrew Cooper
2024-10-15 10:00                     ` Borislav Petkov
2024-10-20 22:44                     ` Josh Poimboeuf
2024-10-20 22:59                       ` Linus Torvalds
2024-10-20 23:11                         ` Josh Poimboeuf
2024-10-20 23:14                           ` Josh Poimboeuf
2024-10-20 23:35                           ` Linus Torvalds
2024-10-23  9:44                             ` Borislav Petkov
2024-10-23 19:17                               ` Linus Torvalds
2024-10-23 20:07                                 ` Linus Torvalds
2024-10-23 23:32                                   ` Linus Torvalds
2024-10-24  2:00                                     ` Linus Torvalds
2024-10-24  9:21                                   ` David Laight [this message]
2024-10-24 16:53                                     ` Linus Torvalds
2024-10-25  8:56                                       ` David Laight
2024-10-25 16:35                                         ` Linus Torvalds
2024-10-21 10:48                         ` Kirill A. Shutemov
2024-10-22  2:36                           ` Linus Torvalds
2024-10-22 10:33                             ` Kirill A. Shutemov
2024-10-22  8:16                           ` Pawan Gupta
2024-10-22 10:44                             ` Kirill A. Shutemov
2024-10-14 16:55                   ` Linus Torvalds
2024-10-16 16:10                     ` Linus Torvalds
2024-10-16 22:02                       ` Andrew Cooper
2024-10-16 22:13                         ` Kirill A. Shutemov
2024-10-16 22:34                           ` Linus Torvalds
2024-10-28 11:29                             ` Kirill A. Shutemov
2024-10-28 18:44                               ` Linus Torvalds
2024-10-28 20:31                                 ` Kirill A. Shutemov
2024-10-28 20:49                                   ` Linus Torvalds
2024-10-16 22:32                         ` Linus Torvalds
2024-10-17 11:00                           ` Borislav Petkov
2024-10-14 11:56           ` Kirill A. Shutemov

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=c40199a2a319440d89bfcc5c06ec4b3a@AcuMS.aculab.com \
    --to=david.laight@aculab.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=jpoimboe@kernel.org \
    --cc=kirill@shutemov.name \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=longman@redhat.com \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=mpe@ellerman.id.au \
    --cc=pawan.kumar.gupta@linux.intel.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).