Received: by 2002:a25:c205:0:0:0:0:0 with SMTP id s5csp1512716ybf; Sun, 1 Mar 2020 11:13:58 -0800 (PST) X-Google-Smtp-Source: APXvYqwTFnOaSpqW5v8dfXP5B31TlOW7ZamyWJ9SQosKw7oaRhygqYHPKPKQc8i4WYjM7WyzcIVD X-Received: by 2002:a9d:3df6:: with SMTP id l109mr10473687otc.284.1583090038252; Sun, 01 Mar 2020 11:13:58 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1583090038; cv=none; d=google.com; s=arc-20160816; b=JRZesqDOM7TznkS4G9XUKpzQgDsZw6Gp68G1+VdLkmksPqkcWys0/4DFqyHzib+Bor ZL9ubEsusFqMtQqDU0jNlC7S0L0XtkCkmH6n1wcc2hodmMDuaqz0PLSd+B0YRn/ic3kP B68qWDR55zhegDo+bhgLGS1c6BbpD0Ng07vc0sa+mWS6lx0VKImgxtl+JkG8q1jkbOQV GN4OloPK+n1lN4A9okixEm/yjGQy3GkieEXs0W5ydXKfd+gQjJBgKqeux020sHmpSr7X LSFJ6vMCCf2OSm+97rjed8WQgyMQIgupHhDB6kNCqETGngHfdcb04BKw/BDrbgHqew1c +qYg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:to:from:subject:message-id:date :mime-version; bh=zNC2T0hLt60hxZU2ALw1d5rG9t+MrQbgwlE91pkiSjU=; b=NgFsyCx0iDQ3Esrw/4VFx46M+PCvR5OolktfC3ar9tNpBE5wHxb8RH+j6Lj83Ldxhj H5Hq2EtfDnq5p7O3m98LwjXJ+tk4cuhvnUVGg4mtuGxtrKx1dXOhVxzg51rv7PdRkT3X mXM2tK5LA4hVLdbr8t3xyad/SKeljzysMkYSXqGcN6DxamILJkotRVeh0CUFqIl6+XSq 4yz4G8DNIabenr7K/JlUXUZPDI3OZd1DJUMdpwpOI+TLUacIA1Y6SJpH/C3GxB8UPNfn ORjZWiViZLmvhkO3kQ6c4ksqUQcZ6gUdw7emuljJcua7tt6NbSbR2bZE+Nj73v50gyGW uNKw== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=appspotmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j134si2565138oib.52.2020.03.01.11.13.46; Sun, 01 Mar 2020 11:13:58 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=appspotmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726829AbgCATNX (ORCPT + 99 others); Sun, 1 Mar 2020 14:13:23 -0500 Received: from mail-il1-f197.google.com ([209.85.166.197]:38685 "EHLO mail-il1-f197.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726525AbgCATNQ (ORCPT ); Sun, 1 Mar 2020 14:13:16 -0500 Received: by mail-il1-f197.google.com with SMTP id i67so9151624ilf.5 for ; Sun, 01 Mar 2020 11:13:15 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=zNC2T0hLt60hxZU2ALw1d5rG9t+MrQbgwlE91pkiSjU=; b=guvBMCodJobWOQ4hm7lGV8HkwXKMWTM9Ex3QXxlnPfzbKV/n0YyQy50NWBJQdbRqEz kG1XK7JUsUe+ID3V7A5P2/WoogI8KPRa1q4YxTEkABnLEpF+jjaDTRZmR2q5FecHXJfE IsxZ8k41SVTqxJf5zRt4sW8QV45vcEYmpD5Tkezgr3//nLIADtATg4tfOiw7sVvvL+Wo pckYqNIaVhY1sLp2w5+i87aQ4xCi5c2lMLQUDVXhVEgiZePeHdooL38Xn/5UAyTI7d3S Nx/omBPJeytOODCVDgli/13oiO3plascB0mOOyvuOSFPfQIrftYUFxxTzF+xTG5uNgJ1 S4FQ== X-Gm-Message-State: ANhLgQ1fmowpXyLpGcXsHoJRxWE0MFdzQ6No0rm+gdqSRCIyu+3Yc+0g MD3hzkUiZs4DXh+3I17rLLvOZYEmencHjbRRDCs7afx0ySBt MIME-Version: 1.0 X-Received: by 2002:a5d:88c9:: with SMTP id i9mr1713101iol.210.1583089994963; Sun, 01 Mar 2020 11:13:14 -0800 (PST) Date: Sun, 01 Mar 2020 11:13:14 -0800 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <000000000000cc1faf059fcfdc73@google.com> Subject: WARNING: lock held when returning to user space in ovl_write_iter From: syzbot To: jiufei.xue@linux.alibaba.com, linux-kernel@vger.kernel.org, linux-unionfs@vger.kernel.org, miklos@szeredi.hu, mszeredi@redhat.com, syzkaller-bugs@googlegroups.com 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 Hello, syzbot found the following crash on: HEAD commit: bdc5461b Add linux-next specific files for 20200224 git tree: linux-next console output: https://syzkaller.appspot.com/x/log.txt?x=10deee65e00000 kernel config: https://syzkaller.appspot.com/x/.config?x=8402e437f1eeea92 dashboard link: https://syzkaller.appspot.com/bug?extid=9331a354f4f624a52a55 compiler: gcc (GCC) 9.0.0 20181231 (experimental) syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1571d22de00000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=175192c3e00000 The bug was bisected to: commit 2406a307ac7ddfd7effeeaff6947149ec6a95b4e Author: Jiufei Xue Date: Wed Nov 20 09:45:26 2019 +0000 ovl: implement async IO routines bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=113c6d29e00000 final crash: https://syzkaller.appspot.com/x/report.txt?x=133c6d29e00000 console output: https://syzkaller.appspot.com/x/log.txt?x=153c6d29e00000 IMPORTANT: if you fix the bug, please add the following tag to the commit: Reported-by: syzbot+9331a354f4f624a52a55@syzkaller.appspotmail.com Fixes: 2406a307ac7d ("ovl: implement async IO routines") ================================================ WARNING: lock held when returning to user space! 5.6.0-rc2-next-20200224-syzkaller #0 Not tainted ------------------------------------------------ syz-executor184/10029 is leaving the kernel with locks still held! 1 lock held by syz-executor184/10029: #0: ffff88809987c418 (sb_writers#3){.+.+}, at: file_start_write include/linux/fs.h:2903 [inline] #0: ffff88809987c418 (sb_writers#3){.+.+}, at: ovl_write_iter+0xcc1/0x1090 fs/overlayfs/file.c:348 --- This bug 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 bug report. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot. For information about bisection process see: https://goo.gl/tpsmEJ#bisection syzbot can test patches for this bug, for details see: https://goo.gl/tpsmEJ#testing-patches