[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <68817ebf-8f3b-c40c-a7d0-82139d9e452b@huaweicloud.com>
Date: Thu, 9 May 2024 20:02:01 +0800
From: Zhang Yi <yi.zhang@...weicloud.com>
To: Kemeng Shi <shikemeng@...weicloud.com>
Cc: linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org, tytso@....edu,
jack@...e.com
Subject: Re: [PATCH 8/9] jbd2: remove dead check of JBD2_UNMOUNT in kjournald2
On 2024/5/6 22:18, Kemeng Shi wrote:
> We always set JBD2_UNMOUNT with j_state_lock held in journal_kill_thread.
> In kjournald2, we check JBD2_UNMOUNT flag two times under the same
> j_state_lock. Then the second check is unnecessary.
> Also see comment in struct journal_s about lock rule of j_flags.
>
> Signed-off-by: Kemeng Shi <shikemeng@...weicloud.com>
Looks good to me.
Reviewed-by: Zhang Yi <yi.zhang@...wei.com>
> ---
> fs/jbd2/journal.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/fs/jbd2/journal.c b/fs/jbd2/journal.c
> index e8f592fbd6e1..ce9004f40ffb 100644
> --- a/fs/jbd2/journal.c
> +++ b/fs/jbd2/journal.c
> @@ -228,8 +228,6 @@ static int kjournald2(void *arg)
> if (transaction && time_after_eq(jiffies,
> transaction->t_expires))
> should_sleep = 0;
> - if (journal->j_flags & JBD2_UNMOUNT)
> - should_sleep = 0;
> if (should_sleep) {
> write_unlock(&journal->j_state_lock);
> schedule();
>
Powered by blists - more mailing lists