All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux regressions mailing list <regressions@lists.linux.dev>,
	"Darrick J. Wong" <djwong@kernel.org>
Cc: Pengfei Xu <pengfei.xu@intel.com>,
	linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	heng.su@intel.com, dchinner@redhat.com, lkp@intel.com
Subject: Re: [Syzkaller & bisect] There is BUG: unable to handle kernel NULL pointer dereference in xfs_extent_free_diff_items in v6.4-rc3
Date: Tue, 23 May 2023 13:08:32 +0700	[thread overview]
Message-ID: <89b7cfee-164a-470e-c375-73b109fdf214@gmail.com> (raw)
In-Reply-To: <aa3fcf2f-013b-358f-e2d3-205e40b6908a@leemhuis.info>

On 5/23/23 00:05, Linux regression tracking (Thorsten Leemhuis) wrote:
> Darrick, sorry for the trouble. Bagas recently out of the blue started
> to help with adding regressions to the tracking. That's great, but OTOH
> it means that it's likely time to write a few things up that are obvious
> to some of us and myself.
> 
> Bagas, please for the foreseeable future don't add regressions found by
> syzkaller to the regression tracking, unless some well known developer
> actually looked into the issue and indicated that it's something that
> needs to be fixed.
> 
> Syzbot is great. But it occasionally does odd things or goes of the
> rails. And in can easily find problems that didn't happen in an earlier
> version, but are unlikely to be encountered by users in practice (aka
> "in the wild"). And we normally don't consider those regressions that
> needs to be fixed.
> 

Oops, at the moment I didn't know how to distinguish true regressions
and issues found by the bot, so I thought that both are regressions.

Thanks for the tip!

-- 
An old man doll... just what I always wanted! - Clara


  reply	other threads:[~2023-05-23  6:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-22  2:07 [Syzkaller & bisect] There is BUG: unable to handle kernel NULL pointer dereference in xfs_extent_free_diff_items in v6.4-rc3 Pengfei Xu
2023-05-22  6:39 ` Bagas Sanjaya
2023-05-22 16:05   ` Darrick J. Wong
2023-05-22 17:05     ` Linux regression tracking (Thorsten Leemhuis)
2023-05-23  6:08       ` Bagas Sanjaya [this message]
2023-05-23  6:44         ` Pengfei Xu
2023-05-23  0:00     ` Eric Biggers
2023-05-23  7:31       ` Dave Chinner
2023-05-23  9:14         ` Pengfei Xu
2023-05-23 21:52           ` Dave Chinner
2023-05-24  2:20             ` Pengfei Xu
2023-05-23 16:50         ` Eric Biggers
2023-05-23 22:16           ` Dave Chinner
2023-05-23 23:46             ` Eric Biggers

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=89b7cfee-164a-470e-c375-73b109fdf214@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=dchinner@redhat.com \
    --cc=djwong@kernel.org \
    --cc=heng.su@intel.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=pengfei.xu@intel.com \
    --cc=regressions@lists.linux.dev \
    /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.