From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] gfs2: ignore rindex_update failure in dinode_dealloc
Date: Fri, 05 May 2023 09:49:22 +0100 [thread overview]
Message-ID: <d402c7018cc89db0f2c7b939c7c17552c0b8219a.camel@redhat.com> (raw)
In-Reply-To: <d388a721-fac9-3b3a-497b-9aee3aec7066@redhat.com>
On Fri, 2023-05-05 at 08:44 +0100, Andrew Price wrote:
> Hi Bob,
>
> On 04/05/2023 18:43, Bob Peterson wrote:
> > Before this patch function gfs2_dinode_dealloc would abort if it
> > got a
> > bad return code from gfs2_rindex_update. The problem is that it
> > left the
> > dinode in the unlinked (not free) state, which meant subsequent
> > fsck
> > would clean it up and flag an error. That meant some of our QE
> > tests
> > would fail.
>
> As I understand it the test is an interrupted rename loop workload
> and
> gfs2_grow at the same time, and the bad return code is -EINTR, right?
>
> > The sole purpose of gfs2_rindex_update, in this code path, is to
> > read in
> > any newer rgrps added by gfs2_grow. But since this is a delete
> > operation
> > it won't actually use any of those new rgrps. It can really only
> > twiddle
> > the bits from "Unlinked" to "Free" in an existing rgrp. Therefore
> > the
> > error should not prevent the transition from unlinked to free.
> >
> > This patch makes gfs2_dinode_dealloc ignore the bad return code and
> > proceed with freeing the dinode so the QE tests will not be tripped
> > up.
>
> Is it really ok to ignore all potential errors here? I wonder if it
> should just ignore -EINTR (or whichever error the test produces) so
> that
> it can still fail well for errors like -EIO.
>
> Cheers,
> Andy
>
Perhaps the more important question is why there are errors there in
the first place?
Steve.
> >
> > Signed-off-by: Bob Peterson <rpeterso@redhat.com>
> > ---
> > ? fs/gfs2/super.c | 4 +---
> > ? 1 file changed, 1 insertion(+), 3 deletions(-)
> >
> > diff --git a/fs/gfs2/super.c b/fs/gfs2/super.c
> > index d3b5c6278be0..1f23d7845123 100644
> > --- a/fs/gfs2/super.c
> > +++ b/fs/gfs2/super.c
> > @@ -1131,9 +1131,7 @@ static int gfs2_dinode_dealloc(struct
> > gfs2_inode *ip)
> > ????????????????return -EIO;
> > ????????}
> > ?
> > -???????error = gfs2_rindex_update(sdp);
> > -???????if (error)
> > -???????????????return error;
> > +???????gfs2_rindex_update(sdp);
>
>
>
> > ?
> > ????????error = gfs2_quota_hold(ip, NO_UID_QUOTA_CHANGE,
> > NO_GID_QUOTA_CHANGE);
> > ????????if (error)
>
next prev parent reply other threads:[~2023-05-05 8:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 17:43 [Cluster-devel] [PATCH] gfs2: ignore rindex_update failure in dinode_dealloc Bob Peterson
2023-05-05 7:44 ` Andrew Price
2023-05-05 8:49 ` Steven Whitehouse [this message]
2023-05-05 12:46 ` Bob Peterson
2023-05-05 12:29 ` Bob Peterson
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=d402c7018cc89db0f2c7b939c7c17552c0b8219a.camel@redhat.com \
--to=swhiteho@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).