From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-il1-f199.google.com (mail-il1-f199.google.com [209.85.166.199]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 4B6E81C68C for ; Tue, 16 Jan 2024 15:54:03 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com Received: by mail-il1-f199.google.com with SMTP id e9e14a558f8ab-35fc70bd879so82628835ab.3 for ; Tue, 16 Jan 2024 07:54:03 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1705420442; x=1706025242; 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=WjLKJeIUZFZaxihu0DFtFUlDAFoZeUeFTWq4/cmqec4=; b=KB4kJMs/TiWydipIIoTLgbxiuPAMzcrv1paoG6JtTycZf1f2vi9+adyHLrQgNxEc3O koxYc+cLBiJ2KdLIg/vU6jnV8b/T3GYAmdf/uaDMVsQNZOSaHoYk7sakl2wxveIxIoEy CEFU82HkF4D+z4XA9eDo3YlmhukFnAX/SUouSAa6wkCMPkWMFHhnTlFi9RXSsZCGreLh 2bzpHF3MoR4bnVb7QFDHv79s6qL/VCJmIG7Ng2nSgcxUHKEv2FbYJJIW3kIHIS5cCKjT /wYl57QRsEevZY1KxjFI2QNSCy8noBUVeZ9HhznGk6VC9/GcW24ftivDljlQJqROEjnD 2U1w== X-Gm-Message-State: AOJu0YyyYu0fSp2peBP9HS6ZEDkKf6gpa9TRelOGjEVhMWRI7u+VEyZt fOK/WcaFBWKGZsLeL0+xQNSWgbftnoMNC8z7wNcRUz816Z75 X-Google-Smtp-Source: AGHT+IFlxGeh6AVV3dy7wQP5TLN9X3pB0gPsRG+Ydvt6+VGd2M1Ue/mlIulGQpjXlNXkskBWVWAg5PmI8zIRlMA1Gap7ra3eI7D3 Precedence: bulk X-Mailing-List: gfs2@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Received: by 2002:a05:6e02:1a03:b0:35f:affb:bd7b with SMTP id s3-20020a056e021a0300b0035faffbbd7bmr1234893ild.2.1705420442573; Tue, 16 Jan 2024 07:54:02 -0800 (PST) Date: Tue, 16 Jan 2024 07:54:02 -0800 In-Reply-To: <0000000000008d00ec05f06bcb35@google.com> X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <000000000000ac2378060f12234c@google.com> Subject: Re: [syzbot] [gfs2?] BUG: unable to handle kernel NULL pointer dereference in gfs2_rindex_update From: syzbot To: agruenba@redhat.com, axboe@kernel.dk, brauner@kernel.org, cluster-devel@redhat.com, gfs2@lists.linux.dev, jack@suse.cz, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, rpeterso@redhat.com, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" syzbot suspects this issue was fixed by commit: commit 6f861765464f43a71462d52026fbddfc858239a5 Author: Jan Kara Date: Wed Nov 1 17:43:10 2023 +0000 fs: Block writes to mounted block devices bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12452f7be80000 start commit: 0a924817d2ed Merge tag '6.2-rc-smb3-client-fixes-part2' of.. git tree: upstream kernel config: https://syzkaller.appspot.com/x/.config?x=4e2d7bfa2d6d5a76 dashboard link: https://syzkaller.appspot.com/bug?extid=2b32df23ff6b5b307565 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14860f08480000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=174d24b0480000 If the result looks correct, please mark the issue as fixed by replying with: #syz fix: fs: Block writes to mounted block devices For information about bisection process see: https://goo.gl/tpsmEJ#bisection