From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756759AbcBXTdI (ORCPT ); Wed, 24 Feb 2016 14:33:08 -0500 Received: from mail-wm0-f43.google.com ([74.125.82.43]:37253 "EHLO mail-wm0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753126AbcBXTdF (ORCPT ); Wed, 24 Feb 2016 14:33:05 -0500 Date: Wed, 24 Feb 2016 20:33:01 +0100 From: "Steinar H. Gunderson" To: Sasha Levin Cc: Greg Kroah-Hartman , linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org, stern@rowland.harvard.edu Subject: Re: [PATCH] Add support for usbfs zerocopy. Message-ID: <20160224193257.GA24059@imap.gmail.com> References: <56CE04C0.4050603@oracle.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <56CE04C0.4050603@oracle.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Feb 24, 2016 at 02:30:08PM -0500, Sasha Levin wrote: > I'm seeing the following warning while fuzzing: > [ 1595.188189] WARNING: CPU: 3 PID: 26063 at mm/page_alloc.c:3207 __alloc_pages_nodemask+0x960/0x29e0() > [ 1595.188287] Modules linked in: > [ 1595.188316] CPU: 3 PID: 26063 Comm: syz-executor Not tainted 4.5.0-rc5-next-20160223-sasha-00022-g03b30f1-dirty #2982 I think it was already established that one could cause kernel warnings if trying to allocate large amounts of memory, but that the usbfs memory limits could curb truly dangerous amounts. Someone please correct me if I'm misunderstanding? /* Steinar */ -- Software Engineer, Google Switzerland