From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 15C49C433EF for ; Fri, 29 Apr 2022 06:42:20 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id A164E6B0073; Fri, 29 Apr 2022 02:42:19 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 9C6516B0074; Fri, 29 Apr 2022 02:42:19 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 890326B0075; Fri, 29 Apr 2022 02:42:19 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (relay.hostedemail.com [64.99.140.28]) by kanga.kvack.org (Postfix) with ESMTP id 7A5456B0073 for ; Fri, 29 Apr 2022 02:42:19 -0400 (EDT) Received: from smtpin05.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay09.hostedemail.com (Postfix) with ESMTP id 5C8A429A07 for ; Fri, 29 Apr 2022 06:42:19 +0000 (UTC) X-FDA: 79408972398.05.E90CDC0 Received: from mail-il1-f198.google.com (mail-il1-f198.google.com [209.85.166.198]) by imf21.hostedemail.com (Postfix) with ESMTP id 1F45D1C006E for ; Fri, 29 Apr 2022 06:42:14 +0000 (UTC) Received: by mail-il1-f198.google.com with SMTP id u11-20020a056e021a4b00b002cc315db462so3110772ilv.4 for ; Thu, 28 Apr 2022 23:42:18 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=l3uvIzx8owff86p9JQl2Fu7AJprV7tqHPmZVvDWo23Y=; b=Oa8PuKCDUWwqi7WMzek8rEaJth4Xr90Bvb9amj5sB00ltaZLe4HtdNxXtD/w5/hR/n 1Dmy9KVvT/LeNIfU+0BH/87IQSdx3BmNCbnrijnE+CQq40C8gjAwmjFuqAWLPC2TRKPE Y57LaVPRCa3iS+EMj2V/9XNXU3s1BhPXYEUiUAXTptdSEO1xUOKBDk14Zb9YmApZoVnv 8P7RGE3rPK0oiBRIR4pY4R0Uii7OT/bYa45LTHVFu4dIdwf1dJWgiSqV0eFP8Blfwkz2 hMEo5yRxgKI0MWvEOh3e7+iz5vqlwSOKNT/ayAkCmyDPmTfUHd1L3P+UV20OgRayTLYw Pyiw== X-Gm-Message-State: AOAM532KIi4ajxGawPQf2CPpLJ3T9TQfS5VYkN5zgJTof4CYgb8IitL0 hBNG9pO8UEvnAIg6Mgw5p3FQTz/oM0o8EDZna05Cx+n4zd5N X-Google-Smtp-Source: ABdhPJx4eNeHQmphQOEWZdtB8HqQTm1RUTsECKQxO5MwZe1wK0DtEboWIgLl45zB6dkp4eQiCGbw1L54lhqfnhXYHV/3KQR/ULPe MIME-Version: 1.0 X-Received: by 2002:a05:6638:cd3:b0:32a:eec5:bbca with SMTP id e19-20020a0566380cd300b0032aeec5bbcamr10551459jak.99.1651214538309; Thu, 28 Apr 2022 23:42:18 -0700 (PDT) Date: Thu, 28 Apr 2022 23:42:18 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <00000000000001044205ddc55870@google.com> Subject: [syzbot] possible deadlock in do_page_fault From: syzbot To: ebiederm@xmission.com, keescook@chromium.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk Content-Type: text/plain; charset="UTF-8" X-Rspamd-Server: rspam04 X-Rspamd-Queue-Id: 1F45D1C006E X-Stat-Signature: 4k51aphimet1kqdmppj5mpuedfefewsa X-Rspam-User: Authentication-Results: imf21.hostedemail.com; dkim=none; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=appspotmail.com (policy=none); spf=pass (imf21.hostedemail.com: domain of 3yohrYgkbAKMVbcNDOOHUDSSLG.JRRJOHXVHUFRQWHQW.FRP@M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com designates 209.85.166.198 as permitted sender) smtp.mailfrom=3yohrYgkbAKMVbcNDOOHUDSSLG.JRRJOHXVHUFRQWHQW.FRP@M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com X-HE-Tag: 1651214534-258684 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: Hello, syzbot found the following issue on: HEAD commit: 0966d385830d riscv: Fix auipc+jalr relocation range checks git tree: git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git fixes console output: https://syzkaller.appspot.com/x/log.txt?x=1128ae72f00000 kernel config: https://syzkaller.appspot.com/x/.config?x=6295d67591064921 dashboard link: https://syzkaller.appspot.com/bug?extid=f8181becdab66ab4b181 compiler: riscv64-linux-gnu-gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 userspace arch: riscv64 Unfortunately, I don't have any reproducer for this issue yet. IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+f8181becdab66ab4b181@syzkaller.appspotmail.com ============================================ WARNING: possible recursive locking detected 5.17.0-rc1-syzkaller-00002-g0966d385830d #0 Not tainted -------------------------------------------- dhcpcd-run-hook/3780 is trying to acquire lock: ffffaf8010608d18 (&mm->mmap_lock){++++}-{3:3}, at: mmap_read_lock include/linux/mmap_lock.h:117 [inline] ffffaf8010608d18 (&mm->mmap_lock){++++}-{3:3}, at: do_page_fault+0x24e/0xa3c arch/riscv/mm/fault.c:285 but task is already holding lock: ffffaf8010608d18 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline] ffffaf8010608d18 (&mm->mmap_lock){++++}-{3:3}, at: setup_arg_pages+0x1aa/0x4b8 fs/exec.c:793 other info that might help us debug this: Possible unsafe locking scenario: CPU0 ---- lock(&mm->mmap_lock); lock(&mm->mmap_lock); *** DEADLOCK *** May be due to missing lock nesting notation 1 lock held by dhcpcd-run-hook/3780: #0: ffffaf8010608d18 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline] #0: ffffaf8010608d18 (&mm->mmap_lock){++++}-{3:3}, at: setup_arg_pages+0x1aa/0x4b8 fs/exec.c:793 stack backtrace: CPU: 1 PID: 3780 Comm: dhcpcd-run-hook Not tainted 5.17.0-rc1-syzkaller-00002-g0966d385830d #0 Hardware name: riscv-virtio,qemu (DT) Call Trace: [] dump_backtrace+0x2e/0x3c arch/riscv/kernel/stacktrace.c:113 [] show_stack+0x34/0x40 arch/riscv/kernel/stacktrace.c:119 [] __dump_stack lib/dump_stack.c:88 [inline] [] dump_stack_lvl+0xe4/0x150 lib/dump_stack.c:106 [] dump_stack+0x1c/0x24 lib/dump_stack.c:113 [] print_deadlock_bug kernel/locking/lockdep.c:2956 [inline] [] check_deadlock kernel/locking/lockdep.c:2999 [inline] [] validate_chain kernel/locking/lockdep.c:3788 [inline] [] __lock_acquire+0x1dcc/0x333e kernel/locking/lockdep.c:5027 [] lock_acquire.part.0+0x1d0/0x424 kernel/locking/lockdep.c:5639 [] lock_acquire+0x54/0x6a kernel/locking/lockdep.c:5612 [] down_read+0x3c/0x54 kernel/locking/rwsem.c:1461 [] mmap_read_lock include/linux/mmap_lock.h:117 [inline] [] do_page_fault+0x24e/0xa3c arch/riscv/mm/fault.c:285 [] ret_from_exception+0x0/0x10 [] __stack_depot_save+0x40/0x4b2 lib/stackdepot.c:360 --- 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.