From: David Sterba <dsterba@suse.cz>
To: fdmanana@kernel.org
Cc: linux-btrfs@vger.kernel.org, Filipe Manana <fdmanana@suse.com>
Subject: Re: [PATCH 0/5] btrfs: fix enospc and transaction aborts during fallocate
Date: Fri, 11 Sep 2020 16:02:16 +0200 [thread overview]
Message-ID: <20200911140216.GQ18399@twin.jikos.cz> (raw)
In-Reply-To: <cover.1599560101.git.fdmanana@suse.com>
On Tue, Sep 08, 2020 at 11:27:19AM +0100, fdmanana@kernel.org wrote:
> From: Filipe Manana <fdmanana@suse.com>
>
> When attempting to fallocate on a large file range with many file extent
> items, the operation can fail with ENOSPC when it shouldn't and, more
> critical, abort the transaction and turn the filesystem to RO mode.
>
> First patch fixes the issue, the remaining just do some cleanups after it.
>
> Filipe Manana (5):
> btrfs: fix metadata reservation for fallocate that leads to
> transaction aborts
> btrfs: remove item_size member of struct btrfs_clone_extent_info
> btrfs: rename struct btrfs_clone_extent_info to a more generic name
> btrfs: rename btrfs_punch_hole_range() to a more generic name
> btrfs: rename btrfs_insert_clone_extent() to a more generic name
Added to misc-next, thanks.
prev parent reply other threads:[~2020-09-11 17:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 10:27 [PATCH 0/5] btrfs: fix enospc and transaction aborts during fallocate fdmanana
2020-09-08 10:27 ` [PATCH 1/5] btrfs: fix metadata reservation for fallocate that leads to transaction aborts fdmanana
2020-09-10 14:48 ` Josef Bacik
2020-09-08 10:27 ` [PATCH 2/5] btrfs: remove item_size member of struct btrfs_clone_extent_info fdmanana
2020-09-10 14:48 ` Josef Bacik
2020-09-08 10:27 ` [PATCH 3/5] btrfs: rename struct btrfs_clone_extent_info to a more generic name fdmanana
2020-09-10 14:48 ` Josef Bacik
2020-09-08 10:27 ` [PATCH 4/5] btrfs: rename btrfs_punch_hole_range() " fdmanana
2020-09-10 14:49 ` Josef Bacik
2020-09-08 10:27 ` [PATCH 5/5] btrfs: rename btrfs_insert_clone_extent() " fdmanana
2020-09-10 14:49 ` Josef Bacik
2020-09-11 14:02 ` 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=20200911140216.GQ18399@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=fdmanana@kernel.org \
--cc=fdmanana@suse.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