From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kees Cook Subject: Re: [kernel-hardening] [PATCH 09/38] usercopy: Mark kmalloc caches as usercopy caches Date: Thu, 14 Nov 2019 13:27:48 -0800 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 Return-path: Content-Disposition: inline In-Reply-To: <201911121313.1097D6EE@keescook> Sender: linux-kernel-owner@vger.kernel.org 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 List-Id: linux-arch.vger.kernel.org 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf1-f196.google.com ([209.85.210.196]:34299 "EHLO mail-pf1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726661AbfKOF3k (ORCPT ); Fri, 15 Nov 2019 00:29:40 -0500 Received: by mail-pf1-f196.google.com with SMTP id n13so5877499pff.1 for ; Thu, 14 Nov 2019 21:29:40 -0800 (PST) Date: Thu, 14 Nov 2019 13:27:48 -0800 From: Kees Cook 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> Sender: linux-arch-owner@vger.kernel.org List-ID: 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 Message-ID: <20191114212748.ACFs-1RTpe63LQKwTd-RFiDm-ZOe7Ywg2KCzl3MTYFU@z> 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