Received-SPF: pass (google.com: domain of linux-ext4+bounces-2715-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) client-ip=147.75.80.249;
Precedence: bulk
MIME-Version: 1.0
References: <20240529092030.9557-1-luis.henriques@linux.dev>
 <20240529092030.9557-2-luis.henriques@linux.dev> <20240529095032.kax3nwtsofyk6qxz@quack3>
In-Reply-To: <20240529095032.kax3nwtsofyk6qxz@quack3>
From: harshad shirwadkar <harshadshirwadkar@gmail.com>
Date: Wed, 29 May 2024 09:52:15 -0700
Message-ID: <CAD+ocbzb5YR2gLxCJcafH4e0Zcq6CCE5Ugibk6urx0yJ8WMfjQ@mail.gmail.com>
Subject: Re: [PATCH v3 1/2] ext4: fix fast commit inode enqueueing during a
 full journal commit
To: Jan Kara <jack@suse.cz>
Cc: "Luis Henriques (SUSE)" <luis.henriques@linux.dev>, "Theodore Ts'o" <tytso@mit.edu>, 
	Andreas Dilger <adilger@dilger.ca>, linux-ext4@vger.kernel.org, 
	linux-kernel@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Looks good!

Reviewed-by: Harshad Shirwadkar <harshadshirwadkar@gmail.com>


On Wed, May 29, 2024 at 2:50=E2=80=AFAM Jan Kara <jack@suse.cz> wrote:
>
> On Wed 29-05-24 10:20:29, Luis Henriques (SUSE) wrote:
> > When a full journal commit is on-going, any fast commit has to be enque=
ued
> > into a different queue: FC_Q_STAGING instead of FC_Q_MAIN.  This enqueu=
eing
> > is done only once, i.e. if an inode is already queued in a previous fas=
t
> > commit entry it won't be enqueued again.  However, if a full commit sta=
rts
> > _after_ the inode is enqueued into FC_Q_MAIN, the next fast commit need=
s to
> > be done into FC_Q_STAGING.  And this is not being done in function
> > ext4_fc_track_template().
> >
> > This patch fixes the issue by re-enqueuing an inode into the STAGING qu=
eue
> > during the fast commit clean-up callback if it has a tid (i_sync_tid)
> > greater than the one being handled.  The STAGING queue will then be spl=
iced
> > back into MAIN.
> >
> > This bug was found using fstest generic/047.  This test creates several=
 32k
> > bytes files, sync'ing each of them after it's creation, and then shutti=
ng
> > down the filesystem.  Some data may be loss in this operation; for exam=
ple a
> > file may have it's size truncated to zero.
> >
> > Signed-off-by: Luis Henriques (SUSE) <luis.henriques@linux.dev>
>
> Looks good to me! Feel free to add:
>
> Reviewed-by: Jan Kara <jack@suse.cz>
>
> Just a typo correction below.
>
> > diff --git a/fs/ext4/fast_commit.c b/fs/ext4/fast_commit.c
> > index 87c009e0c59a..088bd509b116 100644
> > --- a/fs/ext4/fast_commit.c
> > +++ b/fs/ext4/fast_commit.c
> > @@ -1282,8 +1282,17 @@ static void ext4_fc_cleanup(journal_t *journal, =
int full, tid_t tid)
> >               list_del_init(&iter->i_fc_list);
> >               ext4_clear_inode_state(&iter->vfs_inode,
> >                                      EXT4_STATE_FC_COMMITTING);
> > -             if (iter->i_sync_tid <=3D tid)
> > +             if (iter->i_sync_tid <=3D tid) {
> >                       ext4_fc_reset_inode(&iter->vfs_inode);
> > +             } else {
> > +                     /*
> > +                      * re-enqueue inode into STAGING, which later wil=
l be
> > +                      * splice back into MAIN
>                            ^^^ spliced
>
> > +                      */
> > +                     list_add_tail(&EXT4_I(&iter->vfs_inode)->i_fc_lis=
t,
> > +                                   &sbi->s_fc_q[FC_Q_STAGING]);
> > +             }
> > +
>
>                                                                 Honza
> --
> Jan Kara <jack@suse.com>
> SUSE Labs, CR