All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Christoph Hellwig <hch@lst.de>,
	richard@nod.at, anton.ivanov@cambridgegreys.com,
	linux-um@lists.infradead.org
Subject: Re: [PATCH, RFC] um: remove set_fs
Date: Fri, 9 Jul 2021 18:57:37 +0200	[thread overview]
Message-ID: <20210709165737.GA24903@lst.de> (raw)
In-Reply-To: <b7b4f02385c2b103d66eadb1dfcff607a28a82b2.camel@sipsolutions.net>

On Fri, Jul 09, 2021 at 04:47:34PM +0200, Johannes Berg wrote:
> Seems to survive my normal (wireless related) tests :)
> 
> But I don't really understand what any of it does, so ...
> 
> In particular, why no pagefaults for kernel addresses?

No idea.  But the existing uaccess_kernel() versions of the user copy
routines assume it, so this patch just keeps that behavior when switching
to the proper helpers.

_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um


  reply	other threads:[~2021-07-09 16:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-09 13:38 [PATCH, RFC] um: remove set_fs Christoph Hellwig
2021-07-09 14:47 ` Johannes Berg
2021-07-09 16:57   ` Christoph Hellwig [this message]
2021-08-23  7:04   ` Christoph Hellwig
2021-08-23  7:14     ` Anton Ivanov
2021-08-23  8:28     ` Anton Ivanov
2021-08-23 12:17       ` Christoph Hellwig
2021-08-23 12:29         ` Anton Ivanov
2021-08-26 19:15           ` Richard Weinberger
2021-08-26 21:12             ` Anton Ivanov
2021-08-26 22:04               ` Richard Weinberger
2021-08-27  5:40                 ` hch

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=20210709165737.GA24903@lst.de \
    --to=hch@lst.de \
    --cc=anton.ivanov@cambridgegreys.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-um@lists.infradead.org \
    --cc=richard@nod.at \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.