All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: bugzilla-daemon@kernel.org
Cc: linux-ext4@vger.kernel.org
Subject: Re: [Bug 216283] New: FUZZ: BUG() triggered in fs/ext4/extent.c:ext4_ext_insert_extent() when mount and operate on crafted image
Date: Tue, 26 Jul 2022 13:10:24 -0700	[thread overview]
Message-ID: <YuBKMLw6dpERM95F@magnolia> (raw)
In-Reply-To: <bug-216283-13602@https.bugzilla.kernel.org/>

If you are going to run some scripted tool to randomly
corrupt the filesystem to find failures, then you have an
ethical and moral responsibility to do some of the work to
narrow down and identify the cause of the failure, not just
throw them at someone to do all the work.

--D

  reply	other threads:[~2022-07-26 20:10 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-26 19:35 [Bug 216283] New: FUZZ: BUG() triggered in fs/ext4/extent.c:ext4_ext_insert_extent() when mount and operate on crafted image bugzilla-daemon
2022-07-26 20:10 ` Darrick J. Wong [this message]
2022-07-27 11:53   ` Lukas Czerner
2022-07-27 23:22     ` Dave Chinner
2022-07-28  2:46       ` Theodore Ts'o
2022-08-02  3:25         ` Dave Chinner
2022-08-17 12:42           ` Zhang Boyang
2022-07-28  7:25       ` Lukas Czerner
2022-08-01 22:45         ` Dave Chinner
2022-08-02  1:06           ` Theodore Ts'o
2022-08-02  9:28           ` Lukas Czerner
2022-07-26 20:10 ` [Bug 216283] " bugzilla-daemon
2022-07-27 11:53 ` bugzilla-daemon
2022-07-27 23:22 ` bugzilla-daemon
2022-07-28  2:47 ` bugzilla-daemon
2022-07-28  7:25 ` bugzilla-daemon
2022-08-01 22:45 ` bugzilla-daemon
2022-08-02  1:06 ` bugzilla-daemon
2022-08-02  3:26 ` bugzilla-daemon
2022-08-02  9:28 ` bugzilla-daemon
2022-08-17 12:42 ` bugzilla-daemon
2022-10-04  9:15 ` bugzilla-daemon
2022-10-04 19:42 ` bugzilla-daemon

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=YuBKMLw6dpERM95F@magnolia \
    --to=djwong@kernel.org \
    --cc=bugzilla-daemon@kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    /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.