From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from casper.infradead.org (casper.infradead.org [90.155.50.34]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id DE4C21EB55 for ; Fri, 26 Jan 2024 17:11:18 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=90.155.50.34 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1706289080; cv=none; b=sCjwSHLR+suAVUKKYI/aUgwGj0nIEz7l8NSU4I3t1qu9E9X5hDlLwdc5EPnlV5Do9CFMRkD60MUSjSsLBf/Rp2r7mJB4RQCncab62LkOEB/xXtXQ4aRZYzIpWT33APa+G1Mm0p5hoVqq/1UzMmiCMROwgRh9fQNY+fIqLvdtvTA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1706289080; c=relaxed/simple; bh=0xnwHPO9EHtMCiD14Ip4N3gyftO2gndKycahftIn+aA=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=jMDGdoPIRjOkWa7xNpDOw33kv6GJs8AqwMW+nV/MSY541fL01mtYhSxv9UrqMjOFx52GuBngmTNCrbTX2hHd8hYxlE0KcRuajNQx8UtRQKmdAmU54xaDYlfzVl1QRSRuhWsL9BFrMf5Q7tqd9VLjLXpBMJ1YIjUkorhfFE83QPA= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=infradead.org; spf=none smtp.mailfrom=infradead.org; dkim=pass (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b=Mizim/PE; arc=none smtp.client-ip=90.155.50.34 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=infradead.org Authentication-Results: smtp.subspace.kernel.org; spf=none smtp.mailfrom=infradead.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b="Mizim/PE" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=casper.20170209; h=In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=zrATycB01Oq4j4FeneTzWEUxpwPXiI/UPirn0ViraPQ=; b=Mizim/PETvaSoJxj3lKnEjL17x VbhXRSDHp3brWIJMgndN4g3NU9NLxulg1HAaz+ya9sIQAM1ehcFewCVHOLRd+smjh+QZfuNzLKtGo 8yJ1oJ+zgO0DdVGl+nE+2pUwS7Q2mwzo0GLdq+596sRVw7XBnuylRET01oJHlapEFvNE83rPf/xbp qpIDvq8yv63maY3wyHJ0Vxrzrexy+F4jjuE8qpX0SFIyMwUIUdjalRJ56VB+fCwrVlk6uhe3b3L7P cctt3t1llmtnILpbYbtHUE7fs1BcFNzBsoafxaXwdjGPdwbu2mVnDS2V/UynFiIYqs5zJc8k5fyB5 nr0WfXiQ==; Received: from willy by casper.infradead.org with local (Exim 4.97.1 #2 (Red Hat Linux)) id 1rTPjW-0000000EHJ0-2Q1F; Fri, 26 Jan 2024 17:11:15 +0000 Date: Fri, 26 Jan 2024 17:11:14 +0000 From: Matthew Wilcox To: Chenyuan Yang Cc: akpm@linux-foundation.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, syzkaller@googlegroups.com, Zijie Zhao , John Hubbard Subject: Re: [Linux Kernel Bug][mm/gup] 3 Warning Crashes: kmalloc bug in gup_test_ioctl, is_valid_gup_args, pin_user_pages_fast Message-ID: References: Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: On Fri, Jan 26, 2024 at 11:04:53AM -0600, Chenyuan Yang wrote: > Dear Developers for Linux Memory Management, > > We encountered 3 warning crashes when testing the memory management > with Syzkaller and our generated specifications: These all come in through gup_test_ioctl(). It's my impression that this is something you can enable to wreak havoc on your kernel and it's not something which should ever be exposed to fuzzers.