Received: by 2002:a05:6a10:eb17:0:0:0:0 with SMTP id hx23csp2762993pxb; Mon, 6 Sep 2021 04:59:18 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw/bsXuilWRNsCPm8Bl36AkRfoP2Mwr2YsbLicmgybUJD9s0L+o2XJ13IFcGtM5G8FZOEze X-Received: by 2002:a05:6638:d43:: with SMTP id d3mr10387183jak.138.1630929557998; Mon, 06 Sep 2021 04:59:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1630929557; cv=none; d=google.com; s=arc-20160816; b=K0nl4hYVh7WmeHoKMJvnxF9mfH9aDNf4YrWoxXTzTXo9SFaDVpd29utUmcjkJWIBFO TsPnoT9u03pJg0cUYzKYlk+Fb4H1zPVkOhS06SOR4UD/CX8VW+DNQ4qcQKe3gQuWn3wV fUKmoqfFERDB8BocvbSPeS8s0DSc7slL6k1HHguXU5uu1RnIWhBLpbjnv0WTySMrdBf9 paon0S0nIL5USrau2Ca1v9XVRQKj0MMRjR53MlUdoS7vmgin5L8GbMBR+kV/srq9UBWz Q5jfT8J7fqoLvnf40YJKGRn3VUBcjlk95N0AfUW/fMT/swcaxkT5y69oijsDlVHsNUiu 7Ojw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=rYVrPklOjlZ/DTkf8/i1JKXm+JEBvWARosNS8hA3YFs=; b=FyJjwbDJS11VfUvYhDJ6JOiSB72RRqZ+I6bFvB90xo+jEDkJI7d0MAiybIyHNx9eNk LUwi7ZJdKfsJ5i/BOlys4U41VzuXBpCTdB3J1JXWlK8HCMnbpWA0YVq10gvVz2RqTML+ cxTpM4Z8UGXPsEXSKtK1C/R231+9nc79/DTUCdAA6yQbt05fXoUaV33diMRDU9ZifMZk B3wMh715k8OUeRK2IaeWC2+fpzWusgbgtCyED4X+QO1US6IxLA02hppY0RNjQLGEMFqa QUtqOGV6nH313VgxS3AKCbLH5Iv0NXpRiMAVPSsjveWesF6PazcI6RWM6wEfltisOKqW dTTQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=temperror (no key for signature) header.i=@szeredi.hu header.s=google header.b=KV0lnYFi; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id k14si7072953ion.22.2021.09.06.04.59.06; Mon, 06 Sep 2021 04:59:17 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=temperror (no key for signature) header.i=@szeredi.hu header.s=google header.b=KV0lnYFi; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S241229AbhIFL6A (ORCPT + 99 others); Mon, 6 Sep 2021 07:58:00 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54778 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229648AbhIFL6A (ORCPT ); Mon, 6 Sep 2021 07:58:00 -0400 Received: from mail-vs1-xe2c.google.com (mail-vs1-xe2c.google.com [IPv6:2607:f8b0:4864:20::e2c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C930EC061575 for ; Mon, 6 Sep 2021 04:56:55 -0700 (PDT) Received: by mail-vs1-xe2c.google.com with SMTP id n63so5335354vsc.11 for ; Mon, 06 Sep 2021 04:56:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=szeredi.hu; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=rYVrPklOjlZ/DTkf8/i1JKXm+JEBvWARosNS8hA3YFs=; b=KV0lnYFiWnxMYCucoCBbhkEgyniUMWkq/TEYXhZMxnyp+VzgevsuCdHAsBVbBFr4Dg zJ/7KSc3FIXxKFuSBpE1mB5h+aQY59cKGj2pvR0GobqjR5nEy384xtqSM2JSiNpgi9ih yeoKEvQPCla+Nvo+33sRmrqf2+LqpO+URR0AM= 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=rYVrPklOjlZ/DTkf8/i1JKXm+JEBvWARosNS8hA3YFs=; b=qB2cjBHfXWPX+SjnoslIM04CLtsUr3+99tHb9p1zVtNJK3/Z+pDpTgbWpG+nbpMmBX Mw/aYIekZUvu+iIqGhwiTiErW6qKxiGji2gUmwwB7rbdA7d6fWDOYqqSbbmkXUVr6KIq FEHpMNxFdK4zk6Lacg2HrMQtDNYOoxUy1EX5hVHwcFD0UeVveKpiZuzqCZFzF5KOjVS3 /KYyzWk7ZYuOwkRK6LCkeHtZhekvq2lyurwtW1R/fl/LOQGFk7yyZNYB+P9jkFWFKN+P TxtSWugP2LMWK9CF25AbsVvJNiqObhQqg4mQd+y/NokyG6dgdwleUYHG6WyCa4CgdXSO eiTA== X-Gm-Message-State: AOAM533v2jszOtiAueCK/PNsvSi2i+7HnFWPkRHJBVHP8o6L9uJa4QY2 yaHE8YxfVubajCmsMI4F9Tt6PJcb7Cty3PYALMPiid7kwpuB8A== X-Received: by 2002:a67:eb45:: with SMTP id x5mr5704172vso.19.1630929414371; Mon, 06 Sep 2021 04:56:54 -0700 (PDT) MIME-Version: 1.0 References: <000000000000bc92ac05cb4ead3e@google.com> In-Reply-To: <000000000000bc92ac05cb4ead3e@google.com> From: Miklos Szeredi Date: Mon, 6 Sep 2021 13:56:43 +0200 Message-ID: Subject: Re: [syzbot] linux-next test error: KASAN: null-ptr-deref Read in fuse_conn_put To: syzbot Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, Linux-Next Mailing List , Stephen Rothwell , syzkaller-bugs Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Thanks, Force pushed fixed commit 660585b56e63 ("fuse: wait for writepages in syncfs") to fuse.git#for-next. This is fixed as far as I'm concerned, not sure how to tell that to syzbot. Thanks, Miklos On Mon, 6 Sept 2021 at 09:34, syzbot wrote: > > Hello, > > syzbot found the following issue on: > > HEAD commit: 14c6345e6e6c Add linux-next specific files for 20210903 > git tree: linux-next > console output: https://syzkaller.appspot.com/x/log.txt?x=164460ed300000 > kernel config: https://syzkaller.appspot.com/x/.config?x=c17400330d618d71 > dashboard link: https://syzkaller.appspot.com/bug?extid=b304e8cb713be5f9d4e1 > compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.1 > > IMPORTANT: if you fix the issue, please add the following tag to the commit: > Reported-by: syzbot+b304e8cb713be5f9d4e1@syzkaller.appspotmail.com > > ================================================================== > BUG: KASAN: null-ptr-deref in instrument_atomic_read include/linux/instrumented.h:71 [inline] > BUG: KASAN: null-ptr-deref in atomic_read include/linux/atomic/atomic-instrumented.h:27 [inline] > BUG: KASAN: null-ptr-deref in fuse_conn_put fs/fuse/inode.c:827 [inline] > BUG: KASAN: null-ptr-deref in fuse_conn_put+0x1d7/0x300 fs/fuse/inode.c:814 > Read of size 4 at addr 0000000000000000 by task syz-fuzzer/6540 > > CPU: 0 PID: 6540 Comm: syz-fuzzer Not tainted 5.14.0-next-20210903-syzkaller #0 > Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 > Call Trace: > __dump_stack lib/dump_stack.c:88 [inline] > dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106 > __kasan_report mm/kasan/report.c:446 [inline] > kasan_report.cold+0x66/0xdf mm/kasan/report.c:459 > check_region_inline mm/kasan/generic.c:183 [inline] > kasan_check_range+0x13d/0x180 mm/kasan/generic.c:189 > instrument_atomic_read include/linux/instrumented.h:71 [inline] > atomic_read include/linux/atomic/atomic-instrumented.h:27 [inline] > fuse_conn_put fs/fuse/inode.c:827 [inline] > fuse_conn_put+0x1d7/0x300 fs/fuse/inode.c:814 > fuse_dev_free+0x155/0x1f0 fs/fuse/inode.c:1324 > fuse_dev_release+0x2a8/0x3f0 fs/fuse/dev.c:2205 > __fput+0x288/0x9f0 fs/file_table.c:280 > task_work_run+0xdd/0x1a0 kernel/task_work.c:164 > tracehook_notify_resume include/linux/tracehook.h:189 [inline] > exit_to_user_mode_loop kernel/entry/common.c:175 [inline] > exit_to_user_mode_prepare+0x27e/0x290 kernel/entry/common.c:209 > __syscall_exit_to_user_mode_work kernel/entry/common.c:291 [inline] > syscall_exit_to_user_mode+0x19/0x60 kernel/entry/common.c:302 > do_syscall_64+0x42/0xb0 arch/x86/entry/common.c:86 > entry_SYSCALL_64_after_hwframe+0x44/0xae > RIP: 0033:0x4af19b > Code: fb ff eb bd e8 a6 b6 fb ff e9 61 ff ff ff cc e8 9b 82 fb ff 48 8b 7c 24 10 48 8b 74 24 18 48 8b 54 24 20 48 8b 44 24 08 0f 05 <48> 3d 01 f0 ff ff 76 20 48 c7 44 24 28 ff ff ff ff 48 c7 44 24 30 > RSP: 002b:000000c0000ef430 EFLAGS: 00000206 ORIG_RAX: 0000000000000003 > RAX: 0000000000000000 RBX: 000000c00001c000 RCX: 00000000004af19b > RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000006 > RBP: 000000c0000ef470 R08: 0000000000000001 R09: 0000000000000000 > R10: 0000000000000000 R11: 0000000000000206 R12: 0000000000000009 > R13: 0000000000000008 R14: 0000000000000200 R15: 000000c0003fe000 > ================================================================== > > > --- > This report is generated by a bot. It may contain errors. > See https://goo.gl/tpsmEJ for more information about syzbot. > syzbot engineers can be reached at syzkaller@googlegroups.com. > > syzbot will keep track of this issue. See: > https://goo.gl/tpsmEJ#status for how to communicate with syzbot.