From: Christoph Hellwig <hch@lst.de>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: user_access_{save,restore}() semantics
Date: Fri, 10 Jul 2020 18:15:27 +0200 [thread overview]
Message-ID: <20200710161527.GA22579@lst.de> (raw)
Hi Peter,
can you explain (and maybe document while we're at it) what the
exact semantics of the user_access_{save,restore} helpers are?
Reverse engineering from the commit text they seem to be about
saving the current uaccess state. But do they also enable/disable
anything?
next reply other threads:[~2020-07-10 16:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 16:15 Christoph Hellwig [this message]
2020-07-10 16:40 ` user_access_{save,restore}() semantics Peter Zijlstra
2020-07-10 16:46 ` Christoph Hellwig
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=20200710161527.GA22579@lst.de \
--to=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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 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.