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 461EEC77B7F for ; Mon, 1 May 2023 04:31:27 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229556AbjEAEbZ (ORCPT ); Mon, 1 May 2023 00:31:25 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34740 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232171AbjEAEbV (ORCPT ); Mon, 1 May 2023 00:31:21 -0400 Received: from mail-il1-f199.google.com (mail-il1-f199.google.com [209.85.166.199]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 74A7CE5B for ; Sun, 30 Apr 2023 21:31:16 -0700 (PDT) Received: by mail-il1-f199.google.com with SMTP id e9e14a558f8ab-32f23e2018fso148233255ab.0 for ; Sun, 30 Apr 2023 21:31:16 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682915475; x=1685507475; h=to:from:subject:message-id:in-reply-to:date:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=MMopvbnl/gI/YDHKMUQoJhnm8zsxWuaap4+5arlbB+g=; b=j5bbotgiu8oBP3IbZhAkjUFk5oAqo12YL0yc7KU7l5dQzFXQB9Qwkn41oRjGrb3IdB Pe9rJAz14VU0m3dYyfSuCvr1kqm7F7jlL/k2IgPUAU6mDwd784UZXBYtKaJLDVLipzKj 3DCDU/rUFCE9lY8nXfLMtO6GemheI2an0IxWLsLurvxmz/7yLp10V04AQUUsz/5APC2t ytVhb72tueOmIVj9uvL46a6udchjoChMw3cLv/uM6dBJZb3pEkRLw2SuqSRLOvnG3bD0 r6Qh/9knFxi1kX9ClKjniD3x9BjpG1rUYHhV1qU31L6scOq8SenSuX5nRnsimCrR6/zm +vBQ== X-Gm-Message-State: AC+VfDzGfqxBkZAq2DQgaiCD2fe/RnDodVxEL8UkfMOFL4q6UlBcuamR iNEr3wcGi9PA5we6prgKZd/R5GKHxe2WC10Dvup6vnmMt5gY X-Google-Smtp-Source: ACHHUZ7Q4rjTeGpf85L1LGOh7wLdCEauIqOMBHRiBNJYJKx9Tuq8Qab9mCWymwv/5AvWALVhHrPjoTTQ0jQIJr2WAoX/JN3/Rsxj MIME-Version: 1.0 X-Received: by 2002:a02:95e4:0:b0:40f:b984:ca85 with SMTP id b91-20020a0295e4000000b0040fb984ca85mr5812640jai.1.1682915475766; Sun, 30 Apr 2023 21:31:15 -0700 (PDT) Date: Sun, 30 Apr 2023 21:31:15 -0700 In-Reply-To: <000000000000de34bd05f3c6fe19@google.com> X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <0000000000001ec6ce05fa9a4bf7@google.com> Subject: Re: [syzbot] [xfs?] BUG: unable to handle kernel paging request in clear_user_rep_good From: syzbot To: almaz.alexandrovich@paragon-software.com, clm@fb.com, djwong@kernel.org, dsterba@suse.com, hch@infradead.org, josef@toxicpanda.com, linux-btrfs@vger.kernel.org, linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org, ntfs3@lists.linux.dev, syzkaller-bugs@googlegroups.com, torvalds@linux-foundation.org, willy@infradead.org Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-xfs@vger.kernel.org syzbot suspects this issue was fixed by commit: commit d2c95f9d6802cc518d71d9795f4d9da54fb4e24d Author: Linus Torvalds Date: Sat Apr 15 20:22:31 2023 +0000 x86: don't use REP_GOOD or ERMS for user memory clearing bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13636ffc280000 start commit: ab072681eabe Merge tag 'irq_urgent_for_v6.2_rc6' of git://.. git tree: upstream kernel config: https://syzkaller.appspot.com/x/.config?x=23330449ad10b66f dashboard link: https://syzkaller.appspot.com/bug?extid=401145a9a237779feb26 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13b3ba9e480000 If the result looks correct, please mark the issue as fixed by replying with: #syz fix: x86: don't use REP_GOOD or ERMS for user memory clearing For information about bisection process see: https://goo.gl/tpsmEJ#bisection