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=-8.4 required=3.0 tests=DKIMWL_WL_MED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,USER_IN_DEF_DKIM_WL 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 5A6EBC2BB86 for ; Thu, 9 Apr 2020 12:55:57 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 318E02078E for ; Thu, 9 Apr 2020 12:55:57 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=google.com header.i=@google.com header.b="fjomRjM4" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726755AbgDIMzz (ORCPT ); Thu, 9 Apr 2020 08:55:55 -0400 Received: from mail-qk1-f195.google.com ([209.85.222.195]:41285 "EHLO mail-qk1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726627AbgDIMzz (ORCPT ); Thu, 9 Apr 2020 08:55:55 -0400 Received: by mail-qk1-f195.google.com with SMTP id y3so3741256qky.8 for ; Thu, 09 Apr 2020 05:55:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=jAXAQOk0ErVc2APrR6OinTn7FZoQNNgdHYwvSLGe2yc=; b=fjomRjM4YA1sWzArY/6IvCLtRmgdXIsOkn+ejcLJ33W+TsvSbfN8V6vZqD8KEv9qcD LKtS1OGfk7WKZ6S63AjKKpNbyLI0IJN//oK3icStX1HZl/UXYsg+xxmWFyuPCdGGqmKb ukFQzIhW9gJx9WRhaPdP00U7BRTn2LvCEXyGmEdaC7Gvp3FEY+G03cReqaYBU61TViY6 R4twEnNB2lbUs9UH0lz8lPiFBIHGLBBQ6D1O+7tOU3GsY/q2672MRWe3Q6bsvR/5lBtE PU6nBXTDuRdNnujb4SkdrR3qWmdF0nGZY4j8FYO1vRvMm6FVFJzMR9BDQWMHyxXbTgjX IW7w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=jAXAQOk0ErVc2APrR6OinTn7FZoQNNgdHYwvSLGe2yc=; b=T0nhthDgMqg38HNy+ePyM6IkMHDx/VqdarslCyXcXhA+oqw70SvpJeK/e5cBd7hMWh WlO7pJy+lJMVuzyA17jwJQ3WjzvveOPTUp7jjPFGxgLLXLlB+jWO0d7RXdiBtQY/Hksw kZK8DGGSBIcboymnrK0CRmNESuaKscEGLzxJ6ad19FOrWRZ/DNoTBSwvzll6T8nc/+og thsYgkLVkNPuqggLNEGq2AydtYVmtGB1toLZTXHgJNC3EQSZ9WUgWDnt6gWnAMsnIsBF 4ObR7DqE/X2Esy1zy8//eiNCMzzwuNJHQfvNf//OeTdWvGJffGeiq9AXgJKTcAQZxNu4 PXOA== X-Gm-Message-State: AGi0PuaDC0Cw2/h8MkyvUJeDnUv//NEwg4DVQjduoYVV7f9LnezIMRPt by2OSk4FGHzv1wohrWHZyDjY72EKaT2V2al5lx0wVA== X-Google-Smtp-Source: APiQypJgYrBXlCxuuAQfsdESu3sOZUB8jewml+8aR9cEdCQX8DHlXGwINB+Y0v2ChKiBtjQlmnBl37BBspufq/L7nls= X-Received: by 2002:a05:620a:348:: with SMTP id t8mr11010209qkm.407.1586436954251; Thu, 09 Apr 2020 05:55:54 -0700 (PDT) MIME-Version: 1.0 References: <20200408014010.80428-1-peterx@redhat.com> <20200408174732.bc448bbe41d190bfe5cc252e@linux-foundation.org> In-Reply-To: <20200408174732.bc448bbe41d190bfe5cc252e@linux-foundation.org> From: Dmitry Vyukov Date: Thu, 9 Apr 2020 14:55:42 +0200 Message-ID: Subject: Re: [PATCH 0/2] mm: Two small fixes for recent syzbot reports To: Andrew Morton Cc: Peter Xu , LKML , Linus Torvalds , Linux-MM Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Apr 9, 2020 at 2:49 AM Andrew Morton wrote: > > 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? The same thing: https://groups.google.com/d/msg/syzkaller-bugs/phowYdNXHck/qU1P0TsjBAAJ linux-next is boot-broken for more than a month and bugs are piling onto bugs, I've seen at least 3 different ones. syzbot can't get any working linux-next build for testing for a very long time now. 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=-8.4 required=3.0 tests=DKIMWL_WL_MED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,USER_IN_DEF_DKIM_WL 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 AA87EC2BA2B for ; Thu, 9 Apr 2020 12:55:56 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 63CF52078E for ; Thu, 9 Apr 2020 12:55:56 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=google.com header.i=@google.com header.b="fjomRjM4" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 63CF52078E Authentication-Results: mail.kernel.org; dmarc=fail (p=reject dis=none) header.from=google.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 0085A8E000D; Thu, 9 Apr 2020 08:55:56 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id EF91A8E0006; Thu, 9 Apr 2020 08:55:55 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id DE86D8E000D; Thu, 9 Apr 2020 08:55:55 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0182.hostedemail.com [216.40.44.182]) by kanga.kvack.org (Postfix) with ESMTP id D1D9F8E0006 for ; Thu, 9 Apr 2020 08:55:55 -0400 (EDT) Received: from smtpin17.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay05.hostedemail.com (Postfix) with ESMTP id 87546181AEF3F for ; Thu, 9 Apr 2020 12:55:55 +0000 (UTC) X-FDA: 76688313870.17.knife76_8b01e0068da53 X-HE-Tag: knife76_8b01e0068da53 X-Filterd-Recvd-Size: 3796 Received: from mail-qk1-f195.google.com (mail-qk1-f195.google.com [209.85.222.195]) by imf30.hostedemail.com (Postfix) with ESMTP for ; Thu, 9 Apr 2020 12:55:55 +0000 (UTC) Received: by mail-qk1-f195.google.com with SMTP id v7so3791914qkc.0 for ; Thu, 09 Apr 2020 05:55:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=jAXAQOk0ErVc2APrR6OinTn7FZoQNNgdHYwvSLGe2yc=; b=fjomRjM4YA1sWzArY/6IvCLtRmgdXIsOkn+ejcLJ33W+TsvSbfN8V6vZqD8KEv9qcD LKtS1OGfk7WKZ6S63AjKKpNbyLI0IJN//oK3icStX1HZl/UXYsg+xxmWFyuPCdGGqmKb ukFQzIhW9gJx9WRhaPdP00U7BRTn2LvCEXyGmEdaC7Gvp3FEY+G03cReqaYBU61TViY6 R4twEnNB2lbUs9UH0lz8lPiFBIHGLBBQ6D1O+7tOU3GsY/q2672MRWe3Q6bsvR/5lBtE PU6nBXTDuRdNnujb4SkdrR3qWmdF0nGZY4j8FYO1vRvMm6FVFJzMR9BDQWMHyxXbTgjX IW7w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=jAXAQOk0ErVc2APrR6OinTn7FZoQNNgdHYwvSLGe2yc=; b=FRJTRkJKofcsGd5ZA02KKBXS0B8cVbh114NUOLlv6oD5EJpD72CgmagxpXf8nwp1JX fzTNb34xxoYFfGssDAcRiibD0MuDnjnaG8oAcwMNcIINUSaMc0JxPY40CYG3xnESeqg/ BbzXXmINhMcadMfgCZsHprgnC/ldmB3dAG2aGpIiEcefIpc0loAFlE0Yfp+UtXwhleo+ XRTXNzaQVRZfi2gHkNo2QiDTNUT4Md+RxLFjF251KosWbLExn+BthKLm1ppzDuVVo5QS ZmrqdZ2PJOYJh7ONP3gXWuyonbWLcO+8wgrfnwkgpt3sAw6uVrLST4pZfVt5sLsC7s9Q YYkQ== X-Gm-Message-State: AGi0PuYCjdBf6uTYuO07oHVJ44wdSXWBnwKWzzf5vnRtZihZD6U7eWVR 0pp97d92gMyeL9+V/gJ/livAIL2uT71+SViVAJrfIQ== X-Google-Smtp-Source: APiQypJgYrBXlCxuuAQfsdESu3sOZUB8jewml+8aR9cEdCQX8DHlXGwINB+Y0v2ChKiBtjQlmnBl37BBspufq/L7nls= X-Received: by 2002:a05:620a:348:: with SMTP id t8mr11010209qkm.407.1586436954251; Thu, 09 Apr 2020 05:55:54 -0700 (PDT) MIME-Version: 1.0 References: <20200408014010.80428-1-peterx@redhat.com> <20200408174732.bc448bbe41d190bfe5cc252e@linux-foundation.org> In-Reply-To: <20200408174732.bc448bbe41d190bfe5cc252e@linux-foundation.org> From: Dmitry Vyukov Date: Thu, 9 Apr 2020 14:55:42 +0200 Message-ID: Subject: Re: [PATCH 0/2] mm: Two small fixes for recent syzbot reports To: Andrew Morton Cc: Peter Xu , LKML , Linus Torvalds , Linux-MM Content-Type: text/plain; charset="UTF-8" X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Thu, Apr 9, 2020 at 2:49 AM Andrew Morton wrote: > > 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? The same thing: https://groups.google.com/d/msg/syzkaller-bugs/phowYdNXHck/qU1P0TsjBAAJ linux-next is boot-broken for more than a month and bugs are piling onto bugs, I've seen at least 3 different ones. syzbot can't get any working linux-next build for testing for a very long time now.