All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+da0fc229cc1ff4bb2e6d@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, osmtendev@gmail.com,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [gfs2?] BUG: unable to handle kernel NULL pointer dereference in gfs2_rgrp_dump
Date: Sun, 05 Nov 2023 07:41:13 -0800	[thread overview]
Message-ID: <0000000000003dc45c06096991ca@google.com> (raw)
In-Reply-To: <CAK6rUAP-bopjVvGxevFKHEgVhYPxQMD-b2TGsmf81QWSYsirvQ@mail.gmail.com>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-and-tested-by: syzbot+da0fc229cc1ff4bb2e6d@syzkaller.appspotmail.com

Tested on:

commit:         8de1e7af Merge branch 'for-next/core' into for-kernelci
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=176d137f680000
kernel config:  https://syzkaller.appspot.com/x/.config?x=f3093f0327aee8b7
dashboard link: https://syzkaller.appspot.com/bug?extid=da0fc229cc1ff4bb2e6d
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
patch:          https://syzkaller.appspot.com/x/patch.diff?x=10c10097680000

Note: testing is done by a robot and is best-effort only.

       reply	other threads:[~2023-11-05 15:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAK6rUAP-bopjVvGxevFKHEgVhYPxQMD-b2TGsmf81QWSYsirvQ@mail.gmail.com>
2023-11-05 15:41 ` syzbot [this message]
2022-12-26 20:40 [syzbot] [gfs2?] BUG: unable to handle kernel NULL pointer dereference in gfs2_rgrp_dump syzbot
2023-08-29  0:46 ` syzbot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0000000000003dc45c06096991ca@google.com \
    --to=syzbot+da0fc229cc1ff4bb2e6d@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=osmtendev@gmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.