Received: by 10.213.65.68 with SMTP id h4csp603934imn; Fri, 6 Apr 2018 06:03:57 -0700 (PDT) X-Google-Smtp-Source: AIpwx48X3eOlcDTJsddCfw0V1/U1IY5RIUShJ0eYAaJZvwKe5SkuA3/fj9laYbwpnR1OTnJlLayL X-Received: by 2002:a17:902:5acf:: with SMTP id g15-v6mr26706886plm.138.1523019837790; Fri, 06 Apr 2018 06:03:57 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1523019837; cv=none; d=google.com; s=arc-20160816; b=wj+sBPqi5LaL7/cot6FcL5/2yoqdAHK7xNzFIPV8jQWfgRI3dyarNW2AfyZJxlpUFk +yV1IXZLBSbOVb9G6uD20bz4DBL6vGohOwaYTMWPDoXjFxYM23vuPH9VSjngfdPXJO9W mU7y5MjqB5txkmKSXcCw9+ENgQDUAGF6fRy5FGgdm0E0Y340Q7qdl23fBipo0PuukWfr 2NSeWvQYeLWZiZdGtnGn1iSA13RHqtC/r9l6cFoCSMB4OauwenkGP907hqaHMdYpP61l +EFUPGT9LufgJWWTDjX3c9FB9rPqnXnlcEZocyN2bjuw0E9apwlw9k/YHJaBtokjiLjk niag== 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:arc-authentication-results; bh=Oc0NmvpDyF9hnFNDW1CyPXvOBNJj3wD8CChuRPfwSio=; b=MXXeb98oNb0GXlMswo+/s5ymM3cc2BmDSz7xIt+mlDdu4naLPSWefObcSW28VscSeR 27c1h7Xv42je08l9yANbY9Y4OUzHDSRo8Mk7LkY7kByn/NBpDIf7arpf4E1wkqF0927q 8L/crLTa+TKZ8lE17DlthWzH1K6A6M1k6O9ngHYDC8wLZeGuDnB9te98siwUass5HlJF fLfgNfLE5+wO5GiWslm6u7XpouGzuo9/mqDcTyWQupRBgtF1JSAf6qGwr6DXS1aLMG4J 285kgKgOZ4WMZnC0tncSVAgKftYVWpXJMvsmpC51t/dUM6oV0O6uvTrJlL6ikQoltF/d 4dPw== 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 e92-v6si4101117pld.16.2018.04.06.06.03.37; Fri, 06 Apr 2018 06:03:57 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=appspotmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752908AbeDFNCE (ORCPT + 99 others); Fri, 6 Apr 2018 09:02:04 -0400 Received: from mail-io0-f200.google.com ([209.85.223.200]:44279 "EHLO mail-io0-f200.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752889AbeDFNCC (ORCPT ); Fri, 6 Apr 2018 09:02:02 -0400 Received: by mail-io0-f200.google.com with SMTP id o132so1106038iod.11 for ; Fri, 06 Apr 2018 06:02:02 -0700 (PDT) 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=Oc0NmvpDyF9hnFNDW1CyPXvOBNJj3wD8CChuRPfwSio=; b=ITvDwzwmkLIMx1qU3KoDp6JDLKJNlCb1s3kzvKgcislG7EkKxO+uLr+lPUUi8crxwH y4+FjxI0ByRH34CmkBVJPTODQLxLMGK7cMmX6v2o/SKK5Pbf1i9Mv8wZ6OpA9TrL3fXY uT1LXbD4gUOkMXDYxHtIWms1okXGX65ynqn32eVr8IPCGkjlNcoBQ5Q0UhZRDUOytKfx BMgGakDvzUmR5kr7RIOZmgyEVyX0XpzQAV4x6CrWAXqW4fvavvDg2Ab/HVU9wuCafPVf 97cHJZUuUywrdVOmLRg5KrSvQUaakRNmhhcAXGHuNnoI44iIhUmiEcPCMLVDIXyNs7Lh yPEw== X-Gm-Message-State: ALQs6tDukOcohnDZthmMsaEPGvQmBEJLkbPd0uRis1etWM6STBmLEii7 gx91OKAOLySFCNOxchZTOSF9tha8AOyZaIEUO3j9wdkg3yrx MIME-Version: 1.0 X-Received: by 2002:a24:1fc8:: with SMTP id d191-v6mr9018295itd.52.1523019721902; Fri, 06 Apr 2018 06:02:01 -0700 (PDT) Date: Fri, 06 Apr 2018 06:02:01 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <00000000000082922905692da9e1@google.com> Subject: WARNING: lock held when returning to user space! From: syzbot To: axboe@kernel.dk, linux-block@vger.kernel.org, linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8"; format=flowed; delsp=yes Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, syzbot hit the following crash on upstream commit 38c23685b273cfb4ccf31a199feccce3bdcb5d83 (Fri Apr 6 04:29:35 2018 +0000) Merge tag 'armsoc-drivers' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc syzbot dashboard link: https://syzkaller.appspot.com/bug?extid=31e8daa8b3fc129e75f2 So far this crash happened 9 times on upstream. C reproducer: https://syzkaller.appspot.com/x/repro.c?id=6407930337296384 syzkaller reproducer: https://syzkaller.appspot.com/x/repro.syz?id=4942413340606464 Raw console output: https://syzkaller.appspot.com/x/log.txt?id=4764483918495744 Kernel config: https://syzkaller.appspot.com/x/.config?id=-5813481738265533882 compiler: gcc (GCC) 8.0.1 20180301 (experimental) IMPORTANT: if you fix the bug, please add the following tag to the commit: Reported-by: syzbot+31e8daa8b3fc129e75f2@syzkaller.appspotmail.com It will help syzbot understand when the bug is fixed. See footer for details. If you forward the report, please keep this part and the footer. ================================================ WARNING: lock held when returning to user space! 4.16.0+ #3 Not tainted ------------------------------------------------ syzkaller433111/4462 is leaving the kernel with locks still held! 1 lock held by syzkaller433111/4462: #0: 0000000003a06fae (&lo->lo_ctl_mutex/1){+.+.}, at: lo_ioctl+0x8d/0x1ec0 drivers/block/loop.c:1363 --- This bug is generated by a dumb bot. It may contain errors. See https://goo.gl/tpsmEJ for details. Direct all questions to syzkaller@googlegroups.com. syzbot will keep track of this bug report. If you forgot to add the Reported-by tag, once the fix for this bug is merged into any tree, please reply to this email with: #syz fix: exact-commit-title If you want to test a patch for this bug, please reply with: #syz test: git://repo/address.git branch and provide the patch inline or as an attachment. To mark this as a duplicate of another syzbot report, please reply with: #syz dup: exact-subject-of-another-report If it's a one-off invalid bug report, please reply with: #syz invalid Note: if the crash happens again, it will cause creation of a new bug report. Note: all commands must start from beginning of the line in the email body.