From mboxrd@z Thu Jan  1 00:00:00 1970
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1752358AbeAGIsj (ORCPT <rfc822;ralf@linux-mips.org> + 1 other);
        Sun, 7 Jan 2018 03:48:39 -0500
Received: from mail-wm0-f54.google.com ([74.125.82.54]:44790 "EHLO
        mail-wm0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751749AbeAGIsh (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Sun, 7 Jan 2018 03:48:37 -0500
X-Google-Smtp-Source: ACJfBoveeclrdkKIrzlKralXoMSdsd2Fr0bJdBy+h821LN9gkLBauD+BM+xK8zbmb9uWCgUGR5g2og==
Date: Sun, 7 Jan 2018 11:48:33 +0300
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
Message-ID: <20180107084833.GA5511@avx2>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.7.2 (2016-11-26)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Return-Path: <linux-kernel-owner@vger.kernel.org>

> 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.