From: Zhang Yi <yi.zhang@huaweicloud.com>
To: Kemeng Shi <shikemeng@huaweicloud.com>
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
tytso@mit.edu, jack@suse.com
Subject: Re: [PATCH 6/6] jbd2: Correct stale comment of release_buffer_page
Date: Wed, 8 Jan 2025 11:27:53 +0800 [thread overview]
Message-ID: <ba8be54a-5293-495d-adae-87d119cff951@huaweicloud.com> (raw)
In-Reply-To: <20241224202707.1530558-7-shikemeng@huaweicloud.com>
On 2024/12/25 4:27, Kemeng Shi wrote:
> Update stale lock info in comment of release_buffer_page.
>
> Signed-off-by: Kemeng Shi <shikemeng@huaweicloud.com>
Looks good to me.
Reviewed-by: Zhang Yi <yi.zhang@huawei.com>
> ---
> fs/jbd2/commit.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/jbd2/commit.c b/fs/jbd2/commit.c
> index 9153ff3a08e7..d812d15f295e 100644
> --- a/fs/jbd2/commit.c
> +++ b/fs/jbd2/commit.c
> @@ -57,8 +57,8 @@ static void journal_end_buffer_io_sync(struct buffer_head *bh, int uptodate)
> * So here, we have a buffer which has just come off the forget list. Look to
> * see if we can strip all buffers from the backing page.
> *
> - * Called under lock_journal(), and possibly under journal_datalist_lock. The
> - * caller provided us with a ref against the buffer, and we drop that here.
> + * Called under j_list_lock. The caller provided us with a ref against the
> + * buffer, and we drop that here.
> */
> static void release_buffer_page(struct buffer_head *bh)
> {
prev parent reply other threads:[~2025-01-08 3:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-24 20:27 [PATCH 0/6] Minor cleanups to jbd2 Kemeng Shi
2024-12-24 20:27 ` [PATCH 1/6] jbd2: remove unused h_jdata flag of handle Kemeng Shi
2025-01-03 14:35 ` Jan Kara
2025-01-08 2:39 ` Zhang Yi
2024-12-24 20:27 ` [PATCH 2/6] jbd2: remove unused return value of jbd2_journal_cancel_revoke Kemeng Shi
2025-01-03 14:37 ` Jan Kara
2025-01-08 2:43 ` Zhang Yi
2024-12-24 20:27 ` [PATCH 3/6] jbd2: remove unused return value of do_readahead Kemeng Shi
2025-01-03 14:39 ` Jan Kara
2025-01-08 2:46 ` Zhang Yi
2024-12-24 20:27 ` [PATCH 4/6] jbd2: remove stale comment of update_t_max_wait Kemeng Shi
2025-01-03 14:39 ` Jan Kara
2025-01-08 3:12 ` Zhang Yi
2024-12-24 20:27 ` [PATCH 5/6] jbd2: correct stale function name in comment Kemeng Shi
2025-01-03 14:36 ` Jan Kara
2025-01-08 3:22 ` Zhang Yi
2024-12-24 20:27 ` [PATCH 6/6] jbd2: Correct stale comment of release_buffer_page Kemeng Shi
2025-01-03 14:44 ` Jan Kara
2025-01-08 3:27 ` Zhang Yi [this message]
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=ba8be54a-5293-495d-adae-87d119cff951@huaweicloud.com \
--to=yi.zhang@huaweicloud.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®