All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: "Theodore Y. Ts'o" <tytso@mit.edu>
Cc: guaneryu@gmail.com, linux-xfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH 0/7] various: test xfs things fixed in 5.10
Date: Tue, 27 Oct 2020 15:27:28 -0700	[thread overview]
Message-ID: <20201027222728.GB1061252@magnolia> (raw)
In-Reply-To: <20201027213231.GG5691@mit.edu>

On Tue, Oct 27, 2020 at 05:32:31PM -0400, Theodore Y. Ts'o wrote:
> On Tue, Oct 27, 2020 at 12:02:31PM -0700, Darrick J. Wong wrote:
> > Hi all,
> > 
> > Here are a bunch of new tests for problems that were fixed in 5.10.
> > Er.... 5.10 and 5.9.  I have not been good at sending to fstests
> > upstream lately. :( :(
> > 
> > If you're going to start using this mess, you probably ought to just
> > pull from my git trees, which are linked below.
> > 
> > This is an extraordinary way to destroy everything.  Enjoy!
> > Comments and questions are, as always, welcome.
> 
> Hey Darrick, on a slightly different topic, you had mentioned on last
> week's ext4 video chat that you had been working on some patches to
> allow specific blocks to be forced to return EIO, at specific times,
> to test how a file system handles errors when writing to data blocks,
> metadata blocks, journal, etc.
> 
> Are there early versions of those patches available for us to play
> with?  I'm interesting in using that infrastructure for adding some
> ext4 tests along those lines.

They're not even early versions; these have been in my fstests tree for
years but I haven't had time to get them upstreamed. :(

https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfstests-dev.git/commit/?h=scrub-media-error-reporting_2020-10-27&id=2cc930d7f0034879218efc2292b7e4eb2aaa3fea

--D

> Thanks!!
> 
> 					- Ted

  reply	other threads:[~2020-10-27 22:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-27 19:02 [PATCH 0/7] various: test xfs things fixed in 5.10 Darrick J. Wong
2020-10-27 19:02 ` [PATCH 1/7] xfs: test fallocate ops when rt extent size is and isn't a power of 2 Darrick J. Wong
2020-10-29  6:13   ` Chandan Babu R
2020-10-27 19:02 ` [PATCH 2/7] xfs: test regression in xfs_bmap_validate_extent Darrick J. Wong
2020-10-29  6:45   ` Chandan Babu R
2020-10-27 19:02 ` [PATCH 3/7] generic: test reflink and copy_file_range behavior with O_SYNC and FS_XFLAG_SYNC files Darrick J. Wong
2020-10-29  9:10   ` Chandan Babu R
2020-10-27 19:02 ` [PATCH 4/7] xfs: test rtalloc alignment and math errors Darrick J. Wong
2020-10-27 19:03 ` [PATCH 5/7] xfs: test mkfs min log size calculation w/ rt volumes Darrick J. Wong
2020-10-27 19:03 ` [PATCH 6/7] xfs: test quota softlimit warning functionality Darrick J. Wong
2020-10-27 19:03 ` [PATCH 7/7] xfs/122: fix test for xfs_attr_shortform_t conversion Darrick J. Wong
2020-10-29 10:12   ` Chandan Babu R
2020-10-29 11:17   ` Amir Goldstein
2020-10-29 18:17     ` Darrick J. Wong
2020-10-27 21:32 ` [PATCH 0/7] various: test xfs things fixed in 5.10 Theodore Y. Ts'o
2020-10-27 22:27   ` Darrick J. Wong [this message]
2020-11-11  0:43 Darrick J. Wong
2020-11-22 14:27 ` Eryu Guan
2020-11-23 18:20   ` Darrick J. Wong

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=20201027222728.GB1061252@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=fstests@vger.kernel.org \
    --cc=guaneryu@gmail.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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.