Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp1144236ybb; Wed, 8 Apr 2020 17:48:56 -0700 (PDT) X-Google-Smtp-Source: APiQypIKSuhUeB2QYdNqllYbAjyKoQcFPtf7fKNvbVlH3T53DlUs+0GMS6J1CcD7ZEYX0nHqANNV X-Received: by 2002:a05:6808:288:: with SMTP id z8mr4466372oic.149.1586393335894; Wed, 08 Apr 2020 17:48:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1586393335; cv=none; d=google.com; s=arc-20160816; b=AiKievSZ1uJDaQw8G1rMIAPYP3hwSQNif5dQ39GxdZi4MhPuVJ3w61G+ZvuXBvv49v 40ZIt0S5ylX2aCjnVeVxpcor/fKM9UjC0nre3IBJiuA6aeDalOqDPro15A0UYM7j6BBl QjOMLnKgCjPhDZarNadszJWiU/43b5HrIetwtIUAWudQsluG5e4eU9Bs0ef0Q/KX5/Z3 V4ta0UNaupLsq5OZk1+3wLfE33F0heDIXYH2x44YgiOnlGRgBy8fCFbVlN8x2Q3lxUnG r21ETqPf093TjvLXHwclILLLJ5C/8qVm7xb6v8IcwNIutZmevK+iaDf/L41amJ/hXkIf k4AQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date :dkim-signature; bh=akKHvduuvat8RHMlzRUv3zf07IyMGJPz1JsRbF5Dy+U=; b=nIAX9cS6D7VbNyZA3z9F9LLwddOteHyOIga7pkO9dZ9vESaxe2OnVD1WkzcDWFACtv dr31GJd42HzwPnPTpuWTk1TXvVthbuNsmdiATQbCt5ETTJ7V/QoGXmIUeAcGALsT0ng4 ucHX+0noJdr9CAJmpfEkY4TvT5uqNgeahb6tbc+GOJ4I0GWT/FNS1C9S8sS02f29vH9l SzFiH56vJn1RydIHMDZsp4H3ZUyOy3QjV1c7gl6DBAMSJm1u4ao+r4a4yToNWLPZOyJ8 RVbD/5sSSloAQOLJJZUqhn+tMUWdU93eskF5Sfi98b9MGU32omx4yb/uCs9U6k+A7c7v Bq1A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=roVYxbKc; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h192si2659014oib.166.2020.04.08.17.48.41; Wed, 08 Apr 2020 17:48:55 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=roVYxbKc; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726575AbgDIArd (ORCPT + 99 others); Wed, 8 Apr 2020 20:47:33 -0400 Received: from mail.kernel.org ([198.145.29.99]:42960 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726536AbgDIArd (ORCPT ); Wed, 8 Apr 2020 20:47:33 -0400 Received: from localhost.localdomain (c-73-231-172-41.hsd1.ca.comcast.net [73.231.172.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 0133720757; Thu, 9 Apr 2020 00:47:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1586393253; bh=2nhQyL/DP2Bqtl9oIGFAy7+8v5UeTnbKXjY+RkRbpl8=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=roVYxbKcHEORNwh41+mXf7j9wcK3jwv5iCNCc4AcMn2EHwtixACSDrRFahGBlKntG rvYwNqbwPt1aTZjAhJZFhzyytVcw10rC202Fnp4zLWhoxet3CAm2GACn5DRJzqfUCC T7UUxAg7xl1/HwHQXBJ8b3OSLZ460IPHgiOYVQMg= Date: Wed, 8 Apr 2020 17:47:32 -0700 From: Andrew Morton To: Peter Xu Cc: linux-kernel@vger.kernel.org, Linus Torvalds , linux-mm@kvack.org Subject: Re: [PATCH 0/2] mm: Two small fixes for recent syzbot reports Message-Id: <20200408174732.bc448bbe41d190bfe5cc252e@linux-foundation.org> In-Reply-To: <20200408014010.80428-1-peterx@redhat.com> References: <20200408014010.80428-1-peterx@redhat.com> X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.31; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 7 Apr 2020 21:40:08 -0400 Peter Xu wrote: > The two patches should fix below syzbot reports: > > BUG: unable to handle kernel paging request in kernel_get_mempolicy > https://lore.kernel.org/lkml/0000000000002b25f105a2a3434d@google.com/ > > WARNING: bad unlock balance in __get_user_pages_remote > https://lore.kernel.org/lkml/00000000000005c65d05a2b90e70@google.com/ (Is there an email address for the syzbot operators?) sysbot does test linux-next, yet these patches sat in linux-next for a month without a peep, but all hell broke loose when they hit Linus's tree. How could this have happened? Possibly I've been carrying a later patch which fixed all this up, but I'm not seeing anything like that. Nothing at all against mm/gup.c.