From: David Sterba <dsterba@suse.cz>
To: fdmanana@kernel.org
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/2] btrfs: fixes for nowait buffered writes
Date: Wed, 2 Nov 2022 17:39:05 +0100 [thread overview]
Message-ID: <20221102163905.GI5824@twin.jikos.cz> (raw)
In-Reply-To: <cover.1667392727.git.fdmanana@suse.com>
On Wed, Nov 02, 2022 at 12:46:34PM +0000, fdmanana@kernel.org wrote:
> From: Filipe Manana <fdmanana@suse.com>
>
> A couple fixes for the recently added support for nowait buffered writes.
> Trivial stuff, one of the bugs was reported sometime ago by the lkp test
> robot.
>
> Filipe Manana (2):
> btrfs: fix nowait buffered write returning -ENOSPC
> btrfs: fix inode reserve space leak due to nowait buffered write
Added to misc-next, thanks.
prev parent reply other threads:[~2022-11-02 16:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 12:46 [PATCH 0/2] btrfs: fixes for nowait buffered writes fdmanana
2022-11-02 12:46 ` [PATCH 1/2] btrfs: fix nowait buffered write returning -ENOSPC fdmanana
2022-11-02 12:46 ` [PATCH 2/2] btrfs: fix inode reserve space leak due to nowait buffered write fdmanana
2022-11-02 14:06 ` [PATCH 0/2] btrfs: fixes for nowait buffered writes Josef Bacik
2022-11-02 16:39 ` David Sterba [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=20221102163905.GI5824@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=fdmanana@kernel.org \
--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