From: Boris Burkov <boris@bur.io>
To: Neal Gompa <ngompa@fedoraproject.org>
Cc: Filipe Manana <fdmanana@kernel.org>,
linux-btrfs@vger.kernel.org, kernel-team@fb.com,
Davide Cavalca <dcavalca@fedoraproject.org>,
Michel Alexandre Salim <salimma@fedoraproject.org>
Subject: Re: [PATCH] btrfs: fix dio continue after short write due to source fault
Date: Wed, 15 Mar 2023 17:52:07 -0700 [thread overview]
Message-ID: <20230316005207.GA11975@zen> (raw)
In-Reply-To: <CAEg-Je_03VLmcS_XzDytKWbkuDPy9DPesGvoPKa74BqzuRnm0A@mail.gmail.com>
On Wed, Mar 15, 2023 at 08:48:04PM -0400, Neal Gompa wrote:
> On Tue, Feb 21, 2023 at 1:52 PM Boris Burkov <boris@bur.io> wrote:
> >
> > On Mon, Feb 20, 2023 at 02:01:39PM +0000, Filipe Manana wrote:
> > > On Sat, Feb 18, 2023 at 2:25 AM Boris Burkov <boris@bur.io> wrote:
> > > >
> > > > Downstream bug report:
> > > > https://bugzilla.redhat.com/show_bug.cgi?id=2169947
> > >
> > > You place this in a Link: tag at the bottom.
> > > Also the previous discussion is useful to be there too:
> > >
> > > Link: https://lore.kernel.org/linux-btrfs/aa1fb69e-b613-47aa-a99e-a0a2c9ed273f@app.fastmail.com/
> >
> > Thank you for the tip, I'll include those in V2.
> >
>
> What happened here? I haven't seen a V2 posted (unless I missed something?).
>
>
>
> --
> Neal Gompa (FAS: ngompa)
I did post a V2 (and a V3), but unfortunately, I found a bug in it since then.
https://lore.kernel.org/linux-btrfs/20230315195231.GW10580@twin.jikos.cz/T/#t
for reference.
V4 with a slightly different approach dropping tomorrow.
Boris
prev parent reply other threads:[~2023-03-16 0:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-18 1:50 [PATCH] btrfs: fix dio continue after short write due to source fault Boris Burkov
2023-02-18 6:11 ` Christoph Hellwig
2023-02-20 14:01 ` Filipe Manana
2023-02-21 18:34 ` Boris Burkov
2023-03-16 0:48 ` Neal Gompa
2023-03-16 0:52 ` Boris Burkov [this message]
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=20230316005207.GA11975@zen \
--to=boris@bur.io \
--cc=dcavalca@fedoraproject.org \
--cc=fdmanana@kernel.org \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=ngompa@fedoraproject.org \
--cc=salimma@fedoraproject.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