From: David Disseldorp <ddiss@suse.de>
To: Filipe Manana <fdmanana@kernel.org>
Cc: Zorro Lang <zlang@redhat.com>,
Omar Sandoval <osandov@osandov.com>,
fstests@vger.kernel.org, linux-btrfs@vger.kernel.org,
kernel-team@fb.com
Subject: Re: [PATCH fstests v2] generic: test Btrfs fsync vs. size-extending prealloc write crash
Date: Fri, 7 Jun 2024 20:21:20 +1000 [thread overview]
Message-ID: <20240607202120.2b6ad335.ddiss@suse.de> (raw)
In-Reply-To: <CAL3q7H6Un3j+BbqHc82D68R3rwmT6Y0XfpOadWxdV=DbSN-hmQ@mail.gmail.com>
On Fri, 7 Jun 2024 11:11:34 +0100, Filipe Manana wrote:
...
> > > As a Signed-off-by tag for David Disseldorp instead of Reviewed-by.
> >
> > Oh, this Signed-off-by tag is generated automatically by:
> >
> > https://lore.kernel.org/fstests/c9e54af5-4370-4d45-a8ed-4098b06b2629@suse.com/T/#m8fc24d233b2cf3a323c94c2b8039c0f043e09023
> >
> > if it's a mistake, I'll change it to Reviewed-by:
>
> That I didn't notice, odd that David replied with Signed-off-by and
> not Reviewed-by.
> (cc'ing him)
Oops, yes that should have been a Reviewed-by, sorry.
Please change it.
Thanks, David
next prev parent reply other threads:[~2024-06-07 10:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-24 20:58 [PATCH v2] btrfs: fix crash on racing fsync and size-extending write into prealloc Omar Sandoval
2024-05-24 20:58 ` [PATCH fstests v2] generic: test Btrfs fsync vs. size-extending prealloc write crash Omar Sandoval
2024-05-26 11:47 ` Filipe Manana
2024-06-07 5:12 ` Zorro Lang
2024-06-07 9:43 ` Filipe Manana
2024-06-07 10:04 ` Zorro Lang
2024-06-07 10:11 ` Filipe Manana
2024-06-07 10:21 ` David Disseldorp [this message]
2024-05-26 11:41 ` [PATCH v2] btrfs: fix crash on racing fsync and size-extending write into prealloc Filipe Manana
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=20240607202120.2b6ad335.ddiss@suse.de \
--to=ddiss@suse.de \
--cc=fdmanana@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=osandov@osandov.com \
--cc=zlang@redhat.com \
/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