Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Omar Sandoval <osandov@osandov.com>
To: Filipe Manana <fdmanana@kernel.org>
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH fstests v3] generic: test Btrfs fsync vs. size-extending prealloc write crash
Date: Tue, 28 May 2024 10:24:11 -0700	[thread overview]
Message-ID: <ZlYTO9FNeYjsFTr6@telecaster.dhcp.thefacebook.com> (raw)
In-Reply-To: <CAL3q7H5z_eYpx8e-J7xPzZMqCxv2xwq9H7ga=8EZdLk7gnT-jQ@mail.gmail.com>

On Tue, May 28, 2024 at 06:21:23PM +0100, Filipe Manana wrote:
> On Tue, May 28, 2024 at 6:13 PM Omar Sandoval <osandov@osandov.com> wrote:
> >
> > From: Omar Sandoval <osandov@fb.com>
> >
> > This is a regression test for a Btrfs bug, but there's nothing
> > Btrfs-specific about it. Since it's a race, we just try to make the race
> > happen in a loop and pass if it doesn't crash after all of our attempts.
> >
> > Signed-off-by: Omar Sandoval <osandov@fb.com>
> 
> Reviewed-by: Filipe Manana <fdmanana@suse.com>
> 
> > ---
> > Changes from v2 [1]:
> >
> > - Rebased on for-next.
> > - Added _require_odirect.
> > - Added FSTYP check to _fixed_by_kernel_commit.
> > - Added Filipe's Reviewed-by.
> 
> It's missing actually, so I replied with it :)
> 
> Thanks.

Oops, I missed a git command somewhere :) thanks!

  reply	other threads:[~2024-05-28 17:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-28 17:13 [PATCH fstests v3] generic: test Btrfs fsync vs. size-extending prealloc write crash Omar Sandoval
2024-05-28 17:21 ` Filipe Manana
2024-05-28 17:24   ` Omar Sandoval [this message]
2024-06-07 10:19 ` Zorro Lang

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=ZlYTO9FNeYjsFTr6@telecaster.dhcp.thefacebook.com \
    --to=osandov@osandov.com \
    --cc=fdmanana@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=kernel-team@fb.com \
    --cc=linux-btrfs@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