From: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
To: Filipe Manana <fdmanana@kernel.org>
Cc: Naohiro Aota <Naohiro.Aota@wdc.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
David Sterba <dsterba@suse.com>,
Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
Filipe Manana <fdmanana@suse.com>,
Josef Bacik <josef@toxicpanda.com>
Subject: Re: [PATCH] btrfs: ensure pages are unlocked on cow_file_range() failure
Date: Thu, 19 May 2022 13:51:34 +0000 [thread overview]
Message-ID: <PH0PR04MB74166AC3EE68193876D5171D9BD09@PH0PR04MB7416.namprd04.prod.outlook.com> (raw)
In-Reply-To: 20220519133850.GA2735952@falcondesktop
On 19/05/2022 15:39, Filipe Manana wrote:
> On Thu, May 19, 2022 at 12:24:00PM +0000, Johannes Thumshirn wrote:
>> What's the status of this patch? It fixes actual errors
>> (hung_tasks) for me.
> Well, there was previous review about it, and nothing was addressed in the
> meanwhile.
The question was about the general status of it, not if we're going to merge
it. I know Josef's reply.
next prev parent reply other threads:[~2022-05-19 13:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-13 3:43 [PATCH] btrfs: ensure pages are unlocked on cow_file_range() failure Naohiro Aota
2021-12-13 10:14 ` Filipe Manana
2021-12-14 12:21 ` Naohiro Aota
2021-12-13 16:08 ` Josef Bacik
2021-12-14 13:04 ` Naohiro Aota
2022-05-19 12:24 ` Johannes Thumshirn
2022-05-19 13:38 ` Filipe Manana
2022-05-19 13:51 ` Johannes Thumshirn [this message]
2022-05-19 16:18 ` David Sterba
2022-06-13 12:21 ` Naohiro Aota
2022-06-13 15:33 ` Filipe Manana
2022-06-14 3:00 ` Naohiro Aota
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=PH0PR04MB74166AC3EE68193876D5171D9BD09@PH0PR04MB7416.namprd04.prod.outlook.com \
--to=johannes.thumshirn@wdc.com \
--cc=Naohiro.Aota@wdc.com \
--cc=dsterba@suse.com \
--cc=fdmanana@kernel.org \
--cc=fdmanana@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=shinichiro.kawasaki@wdc.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 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.