mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "wangjianjian (C)" <wangjianjian3@huawei.com>
To: Kemeng Shi <shikemeng@huaweicloud.com>, <tytso@mit.edu>, <jack@suse.com>
Cc: <linux-ext4@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 6/8] ext4: move escape handle to futher improve jbd2_journal_write_metadata_buffer
Date: Wed, 7 Aug 2024 15:41:12 +0800	[thread overview]
Message-ID: <2eb72bf1-8c15-40f7-98fe-156c91ab9191@huawei.com> (raw)
In-Reply-To: <20240731092910.2383048-7-shikemeng@huaweicloud.com>

On 2024/7/31 17:29, Kemeng Shi wrote:
> Move escape handle to futher improve code readability and remove some
> repeat check.
Should subject prefix "ext4" be "jbd2" ?

> 
> Signed-off-by: Kemeng Shi <shikemeng@huaweicloud.com>
> ---
>   fs/jbd2/journal.c | 49 +++++++++++++++++++++++------------------------
>   1 file changed, 24 insertions(+), 25 deletions(-)
> 
> diff --git a/fs/jbd2/journal.c b/fs/jbd2/journal.c
> index f17d05bc61df..85273fb1accb 100644
> --- a/fs/jbd2/journal.c
> +++ b/fs/jbd2/journal.c
> @@ -281,6 +281,16 @@ static void journal_kill_thread(journal_t *journal)
>   	write_unlock(&journal->j_state_lock);
>   }
>   
> +static inline bool jbd2_data_needs_escaping(char *data)
> +{
> +	return *((__be32 *)data) == cpu_to_be32(JBD2_MAGIC_NUMBER);
> +}
> +
> +static inline void jbd2_data_do_escape(char *data)
> +{
> +	*((unsigned int *)data) = 0;
> +}
> +
>   /*
>    * jbd2_journal_write_metadata_buffer: write a metadata buffer to the journal.
>    *
> @@ -319,7 +329,6 @@ int jbd2_journal_write_metadata_buffer(transaction_t *transaction,
>   				  sector_t blocknr)
>   {
>   	int do_escape = 0;
> -	char *mapped_data;
>   	struct buffer_head *new_bh;
>   	struct folio *new_folio;
>   	unsigned int new_offset;
> @@ -350,8 +359,13 @@ int jbd2_journal_write_metadata_buffer(transaction_t *transaction,
>   	if (jh_in->b_frozen_data) {
>   		new_folio = virt_to_folio(jh_in->b_frozen_data);
>   		new_offset = offset_in_folio(new_folio, jh_in->b_frozen_data);
> -		mapped_data = jh_in->b_frozen_data;
> +		do_escape = jbd2_data_needs_escaping(jh_in->b_frozen_data);
> +		if (do_escape)
> +			jbd2_data_do_escape(jh_in->b_frozen_data);
>   	} else {
> +		char *tmp;
> +		char *mapped_data;
> +
>   		new_folio = bh_in->b_folio;
>   		new_offset = offset_in_folio(new_folio, bh_in->b_data);
>   		mapped_data = kmap_local_folio(new_folio, new_offset);
> @@ -363,21 +377,13 @@ int jbd2_journal_write_metadata_buffer(transaction_t *transaction,
>   		 */
>   		jbd2_buffer_frozen_trigger(jh_in, mapped_data,
>   					   jh_in->b_triggers);
> -	}
> -
> -	/*
> -	 * Check for escaping
> -	 */
> -	if (*((__be32 *)mapped_data) == cpu_to_be32(JBD2_MAGIC_NUMBER))
> -		do_escape = 1;
> -	if (!jh_in->b_frozen_data)
> +		do_escape = jbd2_data_needs_escaping(mapped_data);
>   		kunmap_local(mapped_data);
> -
> -	/*
> -	 * Do we need to do a data copy?
> -	 */
> -	if (do_escape && !jh_in->b_frozen_data) {
> -		char *tmp;
> +		/*
> +		 * Do we need to do a data copy?
> +		 */
> +		if (!do_escape)
> +			goto escape_done;
>   
>   		spin_unlock(&jh_in->b_state_lock);
>   		tmp = jbd2_alloc(bh_in->b_size, GFP_NOFS);
> @@ -404,17 +410,10 @@ int jbd2_journal_write_metadata_buffer(transaction_t *transaction,
>   copy_done:
>   		new_folio = virt_to_folio(jh_in->b_frozen_data);
>   		new_offset = offset_in_folio(new_folio, jh_in->b_frozen_data);
> +		jbd2_data_do_escape(jh_in->b_frozen_data);
>   	}
>   
> -	/*
> -	 * Did we need to do an escaping?  Now we've done all the
> -	 * copying, we can finally do so.
> -	 * b_frozen_data is from jbd2_alloc() which always provides an
> -	 * address from the direct kernels mapping.
> -	 */
> -	if (do_escape)
> -		*((unsigned int *)jh_in->b_frozen_data) = 0;
> -
> +escape_done:
>   	folio_set_bh(new_bh, new_folio, new_offset);
>   	new_bh->b_size = bh_in->b_size;
>   	new_bh->b_bdev = journal->j_dev;
-- 
Regards


  parent reply	other threads:[~2024-08-07  7:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-31  9:29 [PATCH v3 0/8] Fix and cleanups to jbd2 Kemeng Shi
2024-07-31  9:29 ` [PATCH v3 1/8] jbd2: correctly compare tids with tid_geq function in jbd2_fc_begin_commit Kemeng Shi
2024-07-31  9:29 ` [PATCH v3 2/8] jbd2: remove dead check in journal_alloc_journal_head Kemeng Shi
2024-07-31  9:29 ` [PATCH v3 3/8] jbd2: remove unused return value of jbd2_fc_release_bufs Kemeng Shi
2024-07-31  9:29 ` [PATCH v3 4/8] jbd2: remove unneeded kmap for jh_in->b_frozen_data in jbd2_journal_write_metadata_buffer Kemeng Shi
2024-07-31 11:54   ` Zhang Yi
2024-07-31  9:29 ` [PATCH v3 5/8] jbd2: remove unneeded done_copy_out variable " Kemeng Shi
2024-07-31 11:57   ` Zhang Yi
2024-07-31  9:29 ` [PATCH v3 6/8] ext4: move escape handle to futher improve jbd2_journal_write_metadata_buffer Kemeng Shi
2024-07-31 12:07   ` Zhang Yi
2024-07-31 12:17   ` Zhang Yi
2024-08-01  1:24     ` Kemeng Shi
2024-08-07  7:41   ` wangjianjian (C) [this message]
2024-08-08  5:30     ` Kemeng Shi
2024-07-31  9:29 ` [PATCH v3 7/8] jbd2: correct comment jbd2_mark_journal_empty Kemeng Shi
2024-07-31  9:29 ` [PATCH v3 8/8] jbd2: remove unneeded check of ret in jbd2_fc_get_buf Kemeng Shi
2024-07-31 12:08   ` Zhang Yi

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=2eb72bf1-8c15-40f7-98fe-156c91ab9191@huawei.com \
    --to=wangjianjian3@huawei.com \
    --cc=jack@suse.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shikemeng@huaweicloud.com \
    --cc=tytso@mit.edu \
    /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

all inboxes | Powered by JetHome®