public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Bill O'Donnell <bodonnel@redhat.com>,
	cem@kernel.org, stable@vger.kernel.org, jlayton@kernel.org,
	linux-xfs@vger.kernel.org, hch@lst.de
Subject: Re: [PATCHSET v2] xfs: proposed bug fixes for 6.13
Date: Wed, 4 Dec 2024 23:57:07 -0800	[thread overview]
Message-ID: <20241205075707.GK7837@frogsfrogsfrogs> (raw)
In-Reply-To: <Z1FPGXpTIJ1Fc2Xy@infradead.org>

On Wed, Dec 04, 2024 at 10:58:33PM -0800, Christoph Hellwig wrote:

<cut out all the hostility>

> What Darrick wrote feels a little snarky, but he has a very valid
> point.  A lot of recent bug fixes come from better test coverage, where
> better test coverage is mostly two new fuzzers hitting things, or
> people using existing code for different things that weren't tested
> much before.  And Darrick is single handedly responsible for a large
> part of the better test coverage, both due to fuzzing and specific
> xfstests.  As someone who's done a fair amount of new development
> recently I'm extremely glad about all this extra coverage.

Aww, thank you! :)

--D

  parent reply	other threads:[~2024-12-05  7:57 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-04  3:02 [PATCHSET v2] xfs: proposed bug fixes for 6.13 Darrick J. Wong
2024-12-04  3:02 ` [PATCH 1/6] xfs: don't move nondir/nonreg temporary repair files to the metadir namespace Darrick J. Wong
2024-12-04  8:24   ` Christoph Hellwig
2024-12-05  6:14     ` Darrick J. Wong
2024-12-05  6:46       ` Christoph Hellwig
2024-12-05  7:16         ` Darrick J. Wong
2024-12-04  3:02 ` [PATCH 2/6] xfs: don't crash on corrupt /quotas dirent Darrick J. Wong
2024-12-04  8:24   ` Christoph Hellwig
2024-12-04  3:03 ` [PATCH 3/6] xfs: check pre-metadir fields correctly Darrick J. Wong
2024-12-04  8:25   ` Christoph Hellwig
2024-12-04  3:03 ` [PATCH 4/6] xfs: fix zero byte checking in the superblock scrubber Darrick J. Wong
2024-12-04  8:27   ` Christoph Hellwig
2024-12-05  5:54     ` Darrick J. Wong
2024-12-05  6:48       ` Christoph Hellwig
2024-12-05  7:17         ` Darrick J. Wong
2024-12-04  3:03 ` [PATCH 5/6] xfs: return from xfs_symlink_verify early on V4 filesystems Darrick J. Wong
2024-12-04  8:27   ` Christoph Hellwig
2024-12-04  3:03 ` [PATCH 6/6] xfs: port xfs_ioc_start_commit to multigrain timestamps Darrick J. Wong
2024-12-04  4:01   ` Jeff Layton
2024-12-04  8:28   ` Christoph Hellwig
2024-12-05  1:26 ` [PATCHSET v2] xfs: proposed bug fixes for 6.13 Bill O'Donnell
2024-12-05  6:42   ` Darrick J. Wong
2024-12-05  6:52     ` Bill O'Donnell
2024-12-05  6:58       ` Christoph Hellwig
2024-12-05  7:04         ` Bill O'Donnell
2024-12-05  7:30           ` Bill O'Donnell
2024-12-05  7:39             ` Darrick J. Wong
2024-12-05  7:33           ` Darrick J. Wong
2024-12-05  7:40             ` Bill O'Donnell
2024-12-05  7:46             ` Bill O'Donnell
2024-12-05  8:02               ` Bill O'Donnell
2024-12-05  8:39                 ` Greg KH
2024-12-05  8:47                   ` Bill O'Donnell
2024-12-05  7:57         ` Darrick J. Wong [this message]
2024-12-05 16:11     ` Bill O'Donnell

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=20241205075707.GK7837@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=bodonnel@redhat.com \
    --cc=cem@kernel.org \
    --cc=hch@infradead.org \
    --cc=hch@lst.de \
    --cc=jlayton@kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox