Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp1616450yba; Sun, 14 Apr 2019 15:33:48 -0700 (PDT) X-Google-Smtp-Source: APXvYqxTfiDF4C3au83gtWDNdfwGRvZqeY0h1sLemayoCGamkJUCmoIlR1y5RjwAddkNsHHnn+jP X-Received: by 2002:a17:902:b68e:: with SMTP id c14mr69726165pls.49.1555281228387; Sun, 14 Apr 2019 15:33:48 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1555281228; cv=none; d=google.com; s=arc-20160816; b=UDBRUng1JJRRuGv2VvFZKqI5gbbZuvFMtxb07mGntrQ7oJKHi5QdvVD31qH6xd9XSJ vE6ABev6lLiiBsQej6zZy9b1jVSB/94Yspi6lwL/Jf+cwXPzWSlFPprkiSnxnVFm31xC nIqgeUpokx++iIzOxgfN09jErqYG01RcTaYfpx7wsBBIvy9Y6IFkVj+EdC5k5vr5kji/ ug3izlPOrqO7m72HbidnRXh7HwN6qwjB13CJ541463jljzpKUOO5rd9ua285fMUmH3SN zufrKnfVO0UAnuJm93w21vPHL21uU8YvwfijhejiTSNNX5wcYoMAO+MB6KO6dTrvj87w APSA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=Nqm2kJlkxd1Xqq8A4tBda54tJo96tJIKSbTasAbCO+k=; b=UAVR5OLdk+s0CtvuQyQqeOnipmEfO1QAJfSbVWpw9eJrskNA8Izu7xROXZ5uFEeeN9 h+yvOW0Gm//gUpNroFdp3Jy1VN4YJTvZS7p4Epq61ZAoMXN6zJE54VKsGSuFHldW/CUt YeP/yFWXEtmMisPg0uBo2+FLAKGGLx6nBWnU5Zhf1ILlSDbCFgYHcf/s2zjHWYnC4Vnz 7tOCPjF90NCS2fGCrgI8MJemWtFfx591+ZsU0d0BXH4+vtVqdB41UDM0RIQAIa4wzJDh zjx8yr+aUy5ntdnELwgkYqWL76MQxuckvL33EkUVWJyVhc/JFLZNkJqrpBal01ueR05Q TipA== ARC-Authentication-Results: i=1; mx.google.com; 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 p88si43912273pfi.142.2019.04.14.15.33.31; Sun, 14 Apr 2019 15:33:48 -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; 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 S1726464AbfDNWcz (ORCPT + 99 others); Sun, 14 Apr 2019 18:32:55 -0400 Received: from Chamillionaire.breakpoint.cc ([146.0.238.67]:48410 "EHLO Chamillionaire.breakpoint.cc" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725772AbfDNWcz (ORCPT ); Sun, 14 Apr 2019 18:32:55 -0400 Received: from fw by Chamillionaire.breakpoint.cc with local (Exim 4.89) (envelope-from ) id 1hFnfw-0006Vz-SC; Mon, 15 Apr 2019 00:32:37 +0200 Date: Mon, 15 Apr 2019 00:32:36 +0200 From: Florian Westphal To: Andy Lutomirski Cc: syzbot , alexl@redhat.com, bridge@lists.linux-foundation.org, coreteam@netfilter.org, cosimo@endlessm.com, davem@davemloft.net, dvyukov@google.com, fw@strlen.de, kadlec@blackhole.kfki.hu, libc-alpha@sourceware.org, linux-kernel@vger.kernel.org, luto@kernel.org, mingo@kernel.org, netdev@vger.kernel.org, netfilter-devel@vger.kernel.org, nicholson@endlessm.com, pablo@netfilter.org, peterz@infradead.org, raji@linux.vnet.ibm.com, stephen@networkplumber.org, syzkaller-bugs@googlegroups.com, tglx@linutronix.de, torvalds@linux-foundation.org, tuliom@linux.vnet.ibm.com Subject: Re: WARNING in compat_copy_entries (2) Message-ID: <20190414223236.amahulln6fw4hwaw@breakpoint.cc> References: <00000000000019eb000586826c2a@google.com> <0E15851D-59E4-455D-985E-65F066E7A85A@amacapital.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0E15851D-59E4-455D-985E-65F066E7A85A@amacapital.net> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Andy Lutomirski wrote: > This is likely a confused bisection. I bet that reverting this patch breaks your test but has nothing to do with the bug. Try reproducing with socketcall() to bisect farther. No need, this WARN_ON can be removed. I'll send a patch.