From: "Darrick J. Wong" <djwong@kernel.org>
To: Chandan Babu R <chandanrlinux@gmail.com>
Cc: linux-xfs@vger.kernel.org, darrick.wong@oracle.com, hch@lst.de,
allison.henderson@oracle.com
Subject: Re: [PATCH V14 05/16] xfs: Check for extent overflow when removing dir entries
Date: Mon, 11 Jan 2021 17:38:26 -0800 [thread overview]
Message-ID: <20210112013826.GM1164246@magnolia> (raw)
In-Reply-To: <20210110160720.3922965-6-chandanrlinux@gmail.com>
On Sun, Jan 10, 2021 at 09:37:09PM +0530, Chandan Babu R wrote:
> Directory entry removal must always succeed; Hence XFS does the
> following during low disk space scenario:
> 1. Data/Free blocks linger until a future remove operation.
> 2. Dabtree blocks would be swapped with the last block in the leaf space
> and then the new last block will be unmapped.
>
> This facility is reused during low inode extent count scenario i.e. this
> commit causes xfs_bmap_del_extent_real() to return -ENOSPC error code so
> that the above mentioned behaviour is exercised causing no change to the
> directory's extent count.
>
> Signed-off-by: Chandan Babu R <chandanrlinux@gmail.com>
Thanks for the minor tweaks since v12,
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
--D
> ---
> fs/xfs/libxfs/xfs_bmap.c | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> diff --git a/fs/xfs/libxfs/xfs_bmap.c b/fs/xfs/libxfs/xfs_bmap.c
> index 32aeacf6f055..6c8f17a0e247 100644
> --- a/fs/xfs/libxfs/xfs_bmap.c
> +++ b/fs/xfs/libxfs/xfs_bmap.c
> @@ -5151,6 +5151,24 @@ xfs_bmap_del_extent_real(
> /*
> * Deleting the middle of the extent.
> */
> +
> + /*
> + * For directories, -ENOSPC is returned since a directory entry
> + * remove operation must not fail due to low extent count
> + * availability. -ENOSPC will be handled by higher layers of XFS
> + * by letting the corresponding empty Data/Free blocks to linger
> + * until a future remove operation. Dabtree blocks would be
> + * swapped with the last block in the leaf space and then the
> + * new last block will be unmapped.
> + */
> + error = xfs_iext_count_may_overflow(ip, whichfork, 1);
> + if (error) {
> + ASSERT(S_ISDIR(VFS_I(ip)->i_mode) &&
> + whichfork == XFS_DATA_FORK);
> + error = -ENOSPC;
> + goto done;
> + }
> +
> old = got;
>
> got.br_blockcount = del->br_startoff - got.br_startoff;
> --
> 2.29.2
>
next prev parent reply other threads:[~2021-01-12 1:39 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-10 16:07 [PATCH V14 00/16] Bail out if transaction can cause extent count to overflow Chandan Babu R
2021-01-10 16:07 ` [PATCH V14 01/16] xfs: Add helper for checking per-inode extent count overflow Chandan Babu R
2021-01-10 16:07 ` [PATCH V14 02/16] xfs: Check for extent overflow when trivally adding a new extent Chandan Babu R
2021-01-10 16:07 ` [PATCH V14 03/16] xfs: Check for extent overflow when punching a hole Chandan Babu R
2021-01-10 16:07 ` [PATCH V14 04/16] xfs: Check for extent overflow when adding dir entries Chandan Babu R
2021-01-12 1:34 ` Darrick J. Wong
2021-01-10 16:07 ` [PATCH V14 05/16] xfs: Check for extent overflow when removing " Chandan Babu R
2021-01-12 1:38 ` Darrick J. Wong [this message]
2021-01-10 16:07 ` [PATCH V14 06/16] xfs: Check for extent overflow when renaming " Chandan Babu R
2021-01-12 1:37 ` Darrick J. Wong
2021-01-10 16:07 ` [PATCH V14 07/16] xfs: Check for extent overflow when adding/removing xattrs Chandan Babu R
2021-01-10 16:07 ` [PATCH V14 08/16] xfs: Check for extent overflow when writing to unwritten extent Chandan Babu R
2021-01-10 16:07 ` [PATCH V14 09/16] xfs: Check for extent overflow when moving extent from cow to data fork Chandan Babu R
2021-01-10 16:07 ` [PATCH V14 10/16] xfs: Check for extent overflow when remapping an extent Chandan Babu R
2021-01-10 16:07 ` [PATCH V14 11/16] xfs: Check for extent overflow when swapping extents Chandan Babu R
2021-01-10 16:07 ` [PATCH V14 12/16] xfs: Introduce error injection to reduce maximum inode fork extent count Chandan Babu R
2021-01-10 16:07 ` [PATCH V14 13/16] xfs: Remove duplicate assert statement in xfs_bmap_btalloc() Chandan Babu R
2021-01-10 16:07 ` [PATCH V14 14/16] xfs: Compute bmap extent alignments in a separate function Chandan Babu R
2021-01-10 16:07 ` [PATCH V14 15/16] xfs: Process allocated extent " Chandan Babu R
2021-01-10 16:07 ` [PATCH V14 16/16] xfs: Introduce error injection to allocate only minlen size extents for files Chandan Babu R
2022-05-23 11:15 ` [PATCH V14 00/16] Bail out if transaction can cause extent count to overflow Amir Goldstein
2022-05-23 15:50 ` Chandan Babu R
2022-05-23 19:06 ` Amir Goldstein
2022-05-25 5:49 ` Amir Goldstein
2022-05-23 22:43 ` Dave Chinner
2022-05-24 5:36 ` Amir Goldstein
2022-05-24 16:05 ` Amir Goldstein
2022-05-25 8:21 ` Dave Chinner
2022-05-25 7:33 ` Dave Chinner
2022-05-25 7:48 ` Amir Goldstein
2022-05-25 8:38 ` Dave Chinner
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=20210112013826.GM1164246@magnolia \
--to=djwong@kernel.org \
--cc=allison.henderson@oracle.com \
--cc=chandanrlinux@gmail.com \
--cc=darrick.wong@oracle.com \
--cc=hch@lst.de \
--cc=linux-xfs@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