From: Alexey Dobriyan <adobriyan@gmail.com>
To: viro@zeniv.linux.org.uk
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] memdup_user() and friends
Date: Sun, 7 Jan 2018 11:48:33 +0300 [thread overview]
Message-ID: <20180107084833.GA5511@avx2> (raw)
> Objections?
No objections in particular except the amount of mirrored allocator
interfaces is getting pretty ridiculous.
Another thing, blindly changing kmalloc+copy_from_user to memdup_user
can be wrong because of GFP_KERNEL_ACCOUNT if the memory is allocated
persistently.
next reply other threads:[~2018-01-07 8:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-07 8:48 Alexey Dobriyan [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-01-07 2:16 [RFC] memdup_user() and friends Al Viro
2018-01-08 14:57 ` Marcelo Ricardo Leitner
2018-01-08 17:26 ` Andy Shevchenko
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=20180107084833.GA5511@avx2 \
--to=adobriyan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).