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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id B7B34C6FD1D for ; Mon, 27 Mar 2023 18:04:03 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232303AbjC0SEC (ORCPT ); Mon, 27 Mar 2023 14:04:02 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42670 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229452AbjC0SEA (ORCPT ); Mon, 27 Mar 2023 14:04:00 -0400 Received: from mail-il1-f206.google.com (mail-il1-f206.google.com [209.85.166.206]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6196B268A for ; Mon, 27 Mar 2023 11:03:59 -0700 (PDT) Received: by mail-il1-f206.google.com with SMTP id q17-20020a056e020c3100b003245df8be9fso6384714ilg.14 for ; Mon, 27 Mar 2023 11:03:59 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679940238; h=to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=PtFBdDBuZWHwp8r6frrUdQqAmuJLKC58weRQJuwp+G4=; b=n47blD1pAyoAGgBlDohh94M1W5wOZH3YdhDEAgPbPf+VmtJw+ixuNHifRfvC963W6M SF6x1Wticlx2zLgGRBYd2jmTwFgBuPTt6/P6mwO6PdBquBFgtjloKayA1uwzRvSLIwBQ ayU+9ugPyIutNchsC65leXco3JEkQxrtahjjfBA6uAwP1uYGXISiLFSWR7maBCSHc3Yq /TRzd7O8OAtTla8PqXzxixPcBc8QIlurY/edg9ihI6YURWEqxgn13m9u0XRmDTaiZFdr rIeZHljm/adg5QfDE/wQ/8D5FYu535CpoWkxeNiBZT4ExIWsNhTICUbzM6/YJ83Hf5XG ti+g== X-Gm-Message-State: AO0yUKXlClSSGtMyMHLy5o93vtxCaGV0ikI4CWkE29Wyq/URHG3KxL4c 1p0z/8qVUcEM56eKH8hJg+x2mlUqTm6ls35sFcotrZ+gDQ/j6N8SxQ== X-Google-Smtp-Source: AK7set89N7ikLO8rxpqpAce4FBxmvYkRm32tsnNSki0SuCecVYDVDT0zP19RMbezxQJVt9P8TlPTuwNwrwPUiQFnff2v4oxL5HWZ MIME-Version: 1.0 X-Received: by 2002:a02:2208:0:b0:3ad:65e:e489 with SMTP id o8-20020a022208000000b003ad065ee489mr5117760jao.1.1679940238739; Mon, 27 Mar 2023 11:03:58 -0700 (PDT) Date: Mon, 27 Mar 2023 11:03:58 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <0000000000002c916d05f7e591b7@google.com> Subject: [syzbot] linux-next boot error: general protection fault in corrupted From: syzbot To: linux-kernel@vger.kernel.org, linux-next@vger.kernel.org, sfr@canb.auug.org.au, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, syzbot found the following issue on: HEAD commit: 7c4a254d78f8 Add linux-next specific files for 20230323 git tree: linux-next console output: https://syzkaller.appspot.com/x/log.txt?x=14001a7ac80000 kernel config: https://syzkaller.appspot.com/x/.config?x=20fd034702e6edd2 dashboard link: https://syzkaller.appspot.com/bug?extid=8fddae658688311a9edc compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/dc0bbbecd2a5/disk-7c4a254d.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/6b2c8c7cfd4b/vmlinux-7c4a254d.xz kernel image: https://storage.googleapis.com/syzbot-assets/ae312a388585/bzImage-7c4a254d.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+8fddae658688311a9edc@syzkaller.appspotmail.com mount: mounting selinuxfs on /sys/fs/selinux failed: No such file or directory mount: mounting mqueue on /dev/mqueue failed: No such file or di[ 19.342818][ T4416] mount (4416) used greatest stack depth: 23336 bytes left rectory mount: mounting hugetlbfs on /dev/hugepages failed: No such file or directory mount: mounting fuse.lxcfs on /var/lib/lxcfs failed: No such file or directory Starting syslogd: [ 19.633755][ T4426] general protection fault, probably for non-canonical address 0xdffffc000000005d: 0000 [#1] PREEMPT SMP KASAN --- 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.