From: Heming Zhao <heming.zhao@suse.com>
To: Joseph Qi <joseph.qi@linux.alibaba.com>, glass.su@suse.com
Cc: ocfs2-devel@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 3/3] ocfs2: adjust spinlock_t ip_lock protection scope
Date: Wed, 9 Oct 2024 10:58:06 +0800 [thread overview]
Message-ID: <262f4d14-1c48-4974-8c14-c01fab7ff98a@suse.com> (raw)
In-Reply-To: <52e66e96-5edc-4b31-bc72-df2cf7881a9e@linux.alibaba.com>
On 10/8/24 15:18, Joseph Qi wrote:
> This is a standalone cleanup, so please send in a separate thread.
>
> Thanks,
> Joseph
No problem.
-Heming
>
> On 9/8/24 10:07 PM, Heming Zhao wrote:
>> Some of the spinlock_t ip_lock protection scopes are incorrect and
>> should follow the usage in 'struct ocfs2_inode_info'.
>>
>> Signed-off-by: Heming Zhao <heming.zhao@suse.com>
>> Reviewed-by: Su Yue <glass.su@suse.com>
>> ---
>> fs/ocfs2/dlmglue.c | 3 ++-
>> fs/ocfs2/inode.c | 5 +++--
>> fs/ocfs2/resize.c | 4 ++--
>> fs/ocfs2/suballoc.c | 2 +-
>> 4 files changed, 8 insertions(+), 6 deletions(-)
>>
>> diff --git a/fs/ocfs2/dlmglue.c b/fs/ocfs2/dlmglue.c
>> index da78a04d6f0b..4a5900c8dc8f 100644
>> --- a/fs/ocfs2/dlmglue.c
>> +++ b/fs/ocfs2/dlmglue.c
>> @@ -2232,6 +2232,8 @@ static int ocfs2_refresh_inode_from_lvb(struct inode *inode)
>> else
>> inode->i_blocks = ocfs2_inode_sector_count(inode);
>> ... ...
prev parent reply other threads:[~2024-10-09 2:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-08 14:07 [PATCH v3 0/3] ocfs2: give ocfs2 the ability to reclaim suballoc free bg Heming Zhao
2024-09-08 14:07 ` [PATCH v3 1/3] " Heming Zhao
2024-09-09 1:02 ` Heming Zhao
2024-10-08 7:16 ` Joseph Qi
2024-10-09 2:56 ` Heming Zhao
2025-11-12 6:59 ` Heming Zhao
2024-09-08 14:07 ` [PATCH v3 2/3] ocfs2: detect released suballocator bg for fh_to_[dentry|parent] Heming Zhao
2024-09-08 14:07 ` [PATCH v3 3/3] ocfs2: adjust spinlock_t ip_lock protection scope Heming Zhao
2024-10-08 7:18 ` Joseph Qi
2024-10-09 2:58 ` Heming Zhao [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=262f4d14-1c48-4974-8c14-c01fab7ff98a@suse.com \
--to=heming.zhao@suse.com \
--cc=glass.su@suse.com \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ocfs2-devel@lists.linux.dev \
/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®