Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp9210891ybc; Sat, 30 Nov 2019 03:17:19 -0800 (PST) X-Google-Smtp-Source: APXvYqwdLwEubnm+LQ/zEtKlAsz5FIIjSNZgxMRbeEEYWvDNmPqm2abPifGddirrJQBdiRz4fR7G X-Received: by 2002:a17:906:25cb:: with SMTP id n11mr64071068ejb.239.1575112639667; Sat, 30 Nov 2019 03:17:19 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1575112639; cv=none; d=google.com; s=arc-20160816; b=E3S4CFDrLsmBIhawLIUC2gaL+I7uzhlFWB3ugzjCHgO24JljjU8RN6EP0a5ecvJwjw +LP8f5uma6h4ulQOjomYw20WQpMw7SN7LFRDVVt7KKzD6covYMlp8TdTlx2ktrUvpFlm TgKCvFDoNQtBR6MNkWVyf8sAe8pjZUCoFEX4CShB4AGJkOZF9MYw6+gcg/Ds9VZGTkZ+ LYaZLo2Q9IvQRKUcwE2V/OYR3Ie7iiMjjbDFVzf7bmaC70uGcuw1XN7n2DL7+7tJR7+z Yj0XzZRzeq7KG1R6N+EY7qAPXSaq/bszEuXeQ/klPrdi4IBXUsW4Rx/tiF+p24z25Txd ULpw== 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:mail-followup-to :message-id:subject:cc:to:from:date; bh=nK84bo79I26klpqARXbDQi+hKmqOSTfyMrPt2eh7N7o=; b=GQFBLEJQyfqYyoLV9Y+/5yLYdQEaY72GygaVsoJxkNZ+vyJ4LdBgvUbG+bGU+1X6QU g1biXRqZE+whkmiezimqc9rKhyesqzEJOHR85F9QX2ES+7ksfJbfee+ptkJALPXszrWQ 4vglDwc0EX+7uD7Si0+FSO04TIFxiw24dk7wDATGSpXI83INwUMpEKrbEw2mGAhOZSfF LPIBd4fPAdoVxmW8Z4PyUtD0NdraZ2DUhFZwNCAcWI2XPXnuwTC4couM7ghKcSgc7Jwo 8JZAWEVQFiUfaCIgXtyMLgsRJbYlSpgKW1SX3PKqew+61GQTnRX2FjOWmLKJgdFZiGHu 98MA== 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 e25si18493675edr.117.2019.11.30.03.16.27; Sat, 30 Nov 2019 03:17:19 -0800 (PST) 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 S1726718AbfK3LHG (ORCPT + 99 others); Sat, 30 Nov 2019 06:07:06 -0500 Received: from mail105.syd.optusnet.com.au ([211.29.132.249]:59983 "EHLO mail105.syd.optusnet.com.au" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725947AbfK3LHG (ORCPT ); Sat, 30 Nov 2019 06:07:06 -0500 Received: from dimstar.local.net (n122-110-44-45.sun2.vic.optusnet.com.au [122.110.44.45]) by mail105.syd.optusnet.com.au (Postfix) with SMTP id 2FB5B3A2E4A for ; Sat, 30 Nov 2019 22:06:45 +1100 (AEDT) Received: (qmail 11625 invoked by uid 501); 30 Nov 2019 11:06:45 -0000 Date: Sat, 30 Nov 2019 22:06:45 +1100 From: Duncan Roe To: Al Viro Cc: cmetcalf@ezchip.com, coreteam@netfilter.org, davem@davemloft.net, dvyukov@google.com, gang.chen.5i5j@gmail.com, kaber@trash.net, kadlec@blackhole.kfki.hu, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, netfilter-devel@vger.kernel.org, pablo@netfilter.org, syzkaller-bugs@googlegroups.com Subject: Re: KASAN: use-after-free Read in blkdev_get Message-ID: <20191130110645.GA4405@dimstar.local.net> Mail-Followup-To: Al Viro , cmetcalf@ezchip.com, coreteam@netfilter.org, davem@davemloft.net, dvyukov@google.com, gang.chen.5i5j@gmail.com, kaber@trash.net, kadlec@blackhole.kfki.hu, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, netfilter-devel@vger.kernel.org, pablo@netfilter.org, syzkaller-bugs@googlegroups.com References: <000000000000e59aab056e8873ae@google.com> <0000000000000beff305981c5ac6@google.com> <20191124193035.GA4203@ZenIV.linux.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191124193035.GA4203@ZenIV.linux.org.uk> User-Agent: Mutt/1.10.1 (2018-07-13) X-Optus-CM-Score: 0 X-Optus-CM-Analysis: v=2.3 cv=LYdCFQXi c=1 sm=1 tr=0 a=4DzML1vCOQ6Odsy8BUtSXQ==:117 a=4DzML1vCOQ6Odsy8BUtSXQ==:17 a=jpOVt7BSZ2e4Z31A5e1TngXxSK0=:19 a=kj9zAlcOel0A:10 a=MeAgGD-zjQ4A:10 a=RSmzAf-M6YYA:10 a=7QvuB2UPAAAA:8 a=edf1wS77AAAA:8 a=hSkVLCK3AAAA:8 a=mzoz-TVAAAAA:20 a=VwQbUJbxAAAA:8 a=kGbAZRCgAAAA:20 a=Vl-jczeOgfUYCQSrvD8A:9 a=CjuIK1q_8ugA:10 a=vVHabExCe68A:10 a=PyAPxfarwdVEPLbpdMBu:22 a=DcSpbTIhAlouE1Uv7lRv:22 a=cQPPKAXgyycSBL8etih5:22 a=AjGcO6oz07-iQ99wixmX:22 a=p-dnK0njbqwfn1k4-x12:22 a=rLkV7i5x5X597yo9dRWc:22 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Nov 24, 2019 at 07:30:35PM +0000, Al Viro wrote: > On Sun, Nov 24, 2019 at 11:07:00AM -0800, syzbot wrote: > > syzbot has bisected this bug to: > > > > commit 77ef8f5177599efd0cedeb52c1950c1bd73fa5e3 > > Author: Chris Metcalf > > Date: Mon Jan 25 20:05:34 2016 +0000 > > > > tile kgdb: fix bug in copy to gdb regs, and optimize memset > > > > bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1131bc0ee00000 > > start commit: f5b7769e Revert "debugfs: inode: debugfs_create_dir uses m.. > > git tree: upstream > > final crash: https://syzkaller.appspot.com/x/report.txt?x=1331bc0ee00000 > > console output: https://syzkaller.appspot.com/x/log.txt?x=1531bc0ee00000 > > kernel config: https://syzkaller.appspot.com/x/.config?x=709f8187af941e84 > > dashboard link: https://syzkaller.appspot.com/bug?extid=eaeb616d85c9a0afec7d > > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=177f898f800000 > > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=147eb85f800000 > > > > Reported-by: syzbot+eaeb616d85c9a0afec7d@syzkaller.appspotmail.com > > Fixes: 77ef8f517759 ("tile kgdb: fix bug in copy to gdb regs, and optimize > > memset") > > > > For information about bisection process see: https://goo.gl/tpsmEJ#bisection > > Seriously? How can the commit in question (limited to arch/tile/kernel/kgdb.c) > possibly affect a bug that manages to produce a crash report with > RSP: 0018:ffffffff82e03eb8 EFLAGS: 00000282 > RAX: 0000000000000000 RBX: ffffffff82e00000 RCX: 0000000000000000 > RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffffff81088779 > RBP: ffffffff82e03eb8 R08: 0000000000000000 R09: 0000000000000001 > R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 > R13: 0000000000000000 R14: 0000000000000000 R15: ffffffff82e00000 > FS: 0000000000000000(0000) GS:ffff88021fc00000(0000) knlGS:0000000000000000 > CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > CR2: 000000c420447ff8 CR3: 0000000213184000 CR4: 00000000001406f0 > DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 > DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 > in it? Unless something very odd has happened to tile, this crash has > been observed on 64bit x86; the names of registers alone are enough > to be certain of that. > > And the binaries produced by an x86 build should not be affected by any > changes in arch/tile; not unless something is very wrong with the build > system. It's not even that this commit has fixed an earlier bug that > used to mask the one manifested here - it really should have had zero > impact on x86 builds, period. > > So I'm sorry, but I'm calling bullshit. Something's quite wrong with > the bot - either its build system or the bisection process. The acid test would be: does reverting that commit make the problem go away? See, for example, https://bugzilla.kernel.org/show_bug.cgi?id=203935 Cheers ... Duncan.