From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=0.3 required=3.0 tests=DATE_IN_PAST_06_12, DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5E659C432C3 for ; Fri, 15 Nov 2019 05:30:06 +0000 (UTC) Received: from mother.openwall.net (mother.openwall.net [195.42.179.200]) by mail.kernel.org (Postfix) with SMTP id AB72A20729 for ; Fri, 15 Nov 2019 05:30:05 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=chromium.org header.i=@chromium.org header.b="atnC2AMF" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org AB72A20729 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=chromium.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=kernel-hardening-return-17364-kernel-hardening=archiver.kernel.org@lists.openwall.com Received: (qmail 32376 invoked by uid 550); 15 Nov 2019 05:29:53 -0000 Mailing-List: contact kernel-hardening-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Received: (qmail 32349 invoked from network); 15 Nov 2019 05:29:52 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=qwWwUvjngD0vGITVGJw2bNFQc6m1rEqC7TEDYhp2gbo=; b=atnC2AMFzcg/i0Mp01bQtIoCfLx+HHbTWM8nHw4lKY3bvK8sTjwuuQEAzd/5lBqjg8 S2gVzJA/HwmQYtqs72pyRN1J6FXkXvof9go4CmLgmO38QZr4HfrNVAzeJS6EmIVf0Xon frtfStys716GXGZIcxrtKpwu1jAmCujAqb+64= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=qwWwUvjngD0vGITVGJw2bNFQc6m1rEqC7TEDYhp2gbo=; b=IeP8cji3EkpguK8xYmqejEcFBT6WryY4GuHC2nAzRL/JhkJ+Ip16pflLbFEmX3+d2V 6o4w8SkuQRV4Si8cnWFO/oBauMEuH/6b80EcQXTkr2LZR9qitE7TL3Z6mbXo9PLcSqj8 xmS/W8ZM3L0TI5ztrAbOR47LQbsKEHpoX33Hfu9fKlehFoxlgri8h0j4Z4nL4/lZoB3F gUjNNAK8AwnDAMeWSG42iu3wi4Na/Zg8pRyhWaVMYwcOFAPYQyURJnzaHc1Uveod1btV thT13PIKga9O+k3ey76P1Lx6Ico4zn1mKfiEBLthmk5xxGjs0FnUVm+yYWH4Jf5YBEyO gF9w== X-Gm-Message-State: APjAAAUlhCNPAh43RdvD43MzZ+f14vebcfspQNG6PEO/JhFcpWc+2iFg bdnmry/5nIHNoL+sXklI/wZ+gA== X-Google-Smtp-Source: APXvYqwt4zb0Je/V6IpxbO3fLLPDi96nB5JTyVu+Y5Gk5ifcWF6G9mnVci2ds1rUWNSyZ5xoFyc++Q== X-Received: by 2002:a62:7c52:: with SMTP id x79mr15159448pfc.18.1573795780005; Thu, 14 Nov 2019 21:29:40 -0800 (PST) Date: Thu, 14 Nov 2019 13:27:48 -0800 From: Kees Cook To: Jiri Slaby , Alexander Viro Cc: linux-kernel@vger.kernel.org, David Windsor , Pekka Enberg , David Rientjes , Joonsoo Kim , Andrew Morton , linux-mm@kvack.org, linux-xfs@vger.kernel.org, Linus Torvalds , Andy Lutomirski , Christoph Hellwig , Christoph Lameter , "David S. Miller" , Laura Abbott , Mark Rutland , "Martin K. Petersen" , Paolo Bonzini , Christian Borntraeger , Christoffer Dall , Dave Kleikamp , Jan Kara , Luis de Bethencourt , Marc Zyngier , Rik van Riel , Matthew Garrett , linux-fsdevel@vger.kernel.org, linux-arch@vger.kernel.org, netdev@vger.kernel.org, kernel-hardening@lists.openwall.com, Vlastimil Babka , Michal Kubecek Subject: Re: [kernel-hardening] [PATCH 09/38] usercopy: Mark kmalloc caches as usercopy caches Message-ID: <201911141327.4DE6510@keescook> References: <1515636190-24061-1-git-send-email-keescook@chromium.org> <1515636190-24061-10-git-send-email-keescook@chromium.org> <9519edb7-456a-a2fa-659e-3e5a1ff89466@suse.cz> <201911121313.1097D6EE@keescook> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201911121313.1097D6EE@keescook> On Tue, Nov 12, 2019 at 01:21:54PM -0800, Kees Cook wrote: > How is iucv the only network protocol that has run into this? Do others > use a bounce buffer? Another solution would be to use a dedicated kmem cache (instead of the shared kmalloc dma one)? -- Kees Cook