From: Christoph Hellwig <hch@infradead.org>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: Alexei Starovoitov <ast@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Question on "uaccess: Add strict non-pagefault kernel-space read function"
Date: Fri, 3 Apr 2020 06:35:33 -0700 [thread overview]
Message-ID: <20200403133533.GA3424@infradead.org> (raw)
Hi Daniel,
I just stumbled over your above commit, and it really confuses me.
Not the newly added functions, which seems perfectly sane, but why you
left the crazy old functions in place instead of investing a little
bit of extra effort to clean the existing mess up and switch everyone
to the sane new variants?
next reply other threads:[~2020-04-03 13:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 13:35 Christoph Hellwig [this message]
2020-04-03 14:20 ` Question on "uaccess: Add strict non-pagefault kernel-space read function" Daniel Borkmann
2020-04-04 9:31 ` Christoph Hellwig
2020-04-07 9:03 ` Daniel Borkmann
2020-04-07 9:33 ` Christoph Hellwig
2020-04-08 0:15 ` Daniel Borkmann
2020-04-03 19:07 ` Thomas Gleixner
2020-04-03 19:09 ` Thomas Gleixner
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=20200403133533.GA3424@infradead.org \
--to=hch@infradead.org \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--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