From: Dave Chinner <david@fromorbit.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 1/2] xfs: reserve quota for dir expansion when linking/unlinking files
Date: Thu, 10 Mar 2022 12:50:49 +1100 [thread overview]
Message-ID: <20220310015049.GA3927073@dread.disaster.area> (raw)
In-Reply-To: <20220309233302.GE8224@magnolia>
On Wed, Mar 09, 2022 at 03:33:02PM -0800, Darrick J. Wong wrote:
> On Thu, Mar 10, 2022 at 08:48:21AM +1100, Dave Chinner wrote:
> > On Wed, Mar 09, 2022 at 11:22:26AM -0800, Darrick J. Wong wrote:
> > > From: Darrick J. Wong <djwong@kernel.org>
> > > if (error)
> > > goto error_return;
> > > }
> > > @@ -2755,6 +2749,7 @@ xfs_remove(
> > > xfs_mount_t *mp = dp->i_mount;
> > > xfs_trans_t *tp = NULL;
> > > int is_dir = S_ISDIR(VFS_I(ip)->i_mode);
> > > + int dontcare;
> > > int error = 0;
> > > uint resblks;
> > >
> > > @@ -2781,22 +2776,13 @@ xfs_remove(
> > > * block from the directory.
> > > */
> > > resblks = XFS_REMOVE_SPACE_RES(mp);
> > > - error = xfs_trans_alloc(mp, &M_RES(mp)->tr_remove, resblks, 0, 0, &tp);
> > > - if (error == -ENOSPC) {
> > > - resblks = 0;
> > > - error = xfs_trans_alloc(mp, &M_RES(mp)->tr_remove, 0, 0, 0,
> > > - &tp);
> > > - }
> > > + error = xfs_trans_alloc_dir(dp, &M_RES(mp)->tr_remove, ip, &resblks,
> > > + &tp, &dontcare);
> > > if (error) {
> > > ASSERT(error != -ENOSPC);
> > > goto std_return;
> > > }
> >
> > So we just ignore -EDQUOT when it is returned in @dontcare? I'd like
> > a comment to explain why we don't care about EDQUOT here, because
> > the next time I look at this I will have forgotten all about this...
>
> Ok. How about:
>
> /*
> * We try to get the real space reservation first, allowing for
> * directory btree deletion(s) implying possible bmap insert(s).
> * If we can't get the space reservation then we use 0 instead,
> * and avoid the bmap btree insert(s) in the directory code by,
> * if the bmap insert tries to happen, instead trimming the LAST
> * block from the directory.
> *
> * Ignore EDQUOT and ENOSPC being returned via nospace_error
> * because the directory code can handle a reservationless
> * update and we don't want to prevent a user from trying to
> * free space by deleting things.
> */
> error = xfs_trans_alloc_dir(...);
Yeah, that looks good.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2022-03-10 1:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 19:22 [PATCHSET v2 0/2] xfs: make quota reservations for directory changes Darrick J. Wong
2022-03-09 19:22 ` [PATCH 1/2] xfs: reserve quota for dir expansion when linking/unlinking files Darrick J. Wong
2022-03-09 21:48 ` Dave Chinner
2022-03-09 23:33 ` Darrick J. Wong
2022-03-10 1:50 ` Dave Chinner [this message]
2022-03-09 19:22 ` [PATCH 2/2] xfs: reserve quota for target dir expansion when renaming files Darrick J. Wong
2022-03-09 22:05 ` Dave Chinner
2022-03-09 23:36 ` Darrick J. Wong
-- strict thread matches above, loose matches on Subject: below --
2022-03-10 21:53 [PATCHSET v3 0/2] xfs: make quota reservations for directory changes Darrick J. Wong
2022-03-10 21:53 ` [PATCH 1/2] xfs: reserve quota for dir expansion when linking/unlinking files Darrick J. Wong
2022-03-10 22:28 ` 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=20220310015049.GA3927073@dread.disaster.area \
--to=david@fromorbit.com \
--cc=djwong@kernel.org \
--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