From: "Michael S. Tsirkin" <mst@redhat.com>
To: Linus Torvalds <torvalds@linuxfoundation.org>
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Tvrtko Ursulin <tursulin@ursulin.net>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Borislav Petkov <bp@alien8.de>,
Tom Lendacky <thomas.lendacky@amd.com>,
Joerg Roedel <joerg.roedel@amd.com>,
"Nikunj A. Dadhania" <nikunj@amd.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
the arch/x86 maintainers <x86@kernel.org>
Subject: Re: Removing __get_user / __put_user for good
Date: Tue, 20 Oct 2026 05:46:29 -0400 [thread overview]
Message-ID: <20261020054227-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAHk-=wipGHx_1Uztmu773yuTM2ka1fq996UmNoJpvKS0gqEdMg@mail.gmail.com>
On Mon, Oct 19, 2026 at 09:25:02PM -1000, Linus Torvalds wrote:
> Bah. I made this branch of mine public because I wanted Michael
> Tsirkin to check the vhost part.
>
> But honestly, the i915 side and the coco/SEV patches are the much more
> interesting ones.
>
> So this brings in some new victims^Hpeople for that git branch to comment on.
>
> It's all in
>
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> uaccess-cleanup
>
> I haven't dared actually boot it yet.
>
> Linus
vpda seems to survive light testing in a VM for me.
Tested-by: Michael S. Tsirkin <mst@redhat.com>
It's still buggy if there is a swapout right before
the access, just like it was previously, but hey.
One splat less. An improvement.
You might want:
Fixes: 42823a871fd4 ("vringh: support VA with iotlb")
with that, vdpa/vhost bits:
Acked-by: Michael S. Tsirkin <mst@redhat.com>
> On Mon, 19 Oct 2026 at 20:51, Linus Torvalds
> <torvalds@linuxfoundation.org> wrote:
> >
> > I have a whole branch that removes __get_user() and __put_user() entirely.
> >
> > Somebody should check that I did it right. But I didn't want to do the
> > pagefault_disable() around the vringh_notify() part, so it's not quite
> > the same as yours.
> >
> > Let me just push it out. I was going to let it simmer, but your email
> > made me go "I should just let more people look at it".
> >
> > Mind taking a look at the 'uaccess-cleanups' branch?
> >
> > It builds for me. That's all the testing it has gotten so far. Blush.
> >
> > Linus
next prev parent reply other threads:[~2026-10-20 9:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6ad07f8a.a0c71a5e.2d2efd.977a@mx.google.com>
[not found] ` <20261018152358-mutt-send-email-mst@kernel.org>
[not found] ` <CAHk-=wiUn9EbV4TJ4J7OPY0fVc3UC+xb-pp=+rg3hRc4jQqihg@mail.gmail.com>
[not found] ` <20261018174250-mutt-send-email-mst@kernel.org>
[not found] ` <376ef9d0-b03f-4f85-aee5-46cf20eb00ae@gmail.com>
[not found] ` <20261020021924-mutt-send-email-mst@kernel.org>
[not found] ` <CAHk-=wjxtzD1TXZr5iWu0p1+Hu0YZP7jbNSwFkp7AJYmhzhVCA@mail.gmail.com>
2026-10-20 7:25 ` Removing __get_user / __put_user for good Linus Torvalds
2026-10-20 9:33 ` Jani Nikula
2026-10-20 9:46 ` Michael S. Tsirkin [this message]
2026-10-20 13:19 ` Ingo Molnar
2026-10-20 18:14 ` Linus Torvalds
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=20261020054227-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=airlied@gmail.com \
--cc=bp@alien8.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joerg.roedel@amd.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=nikunj@amd.com \
--cc=rodrigo.vivi@intel.com \
--cc=simona@ffwll.ch \
--cc=thomas.lendacky@amd.com \
--cc=torvalds@linuxfoundation.org \
--cc=tursulin@ursulin.net \
--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