From: Joseph Qi <joseph.qi@linux.alibaba.com>
To: Heming Zhao <heming.zhao@suse.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: ocfs2-devel@lists.linux.dev, linux-kernel@vger.kernel.org,
syzbot+f7af59df5d6b25f0febd@syzkaller.appspotmail.com
Subject: Re: [PATCH] ocfs2: cancel dqi_sync_work before freeing oinfo
Date: Wed, 4 Sep 2024 11:27:47 +0800 [thread overview]
Message-ID: <e1496ade-7505-47bb-ac96-4dd48e2e530f@linux.alibaba.com> (raw)
In-Reply-To: <0d6730e8-9a58-45ba-9e57-c22039f03253@suse.com>
On 9/4/24 10:56 AM, Heming Zhao wrote:
> On 9/4/24 10:09, Joseph Qi wrote:
>> ocfs2_global_read_info() will schedule dqi_sync_work. So any error
>> occurs after it, we have to cancel this delayed work first before
>> freeing oinfo, otherwise it will trigger the following warning with
>> CONFIG_DEBUG_OBJECTS_* enabled:
>>
>> ODEBUG: free active (active state 0) object: 00000000d8b0ce28 object type: timer_list hint: qsync_work_fn+0x0/0x16c
>>
>> Link: https://syzkaller.appspot.com/bug?extid=f7af59df5d6b25f0febd
>> Reported-by: syzbot+f7af59df5d6b25f0febd@syzkaller.appspotmail.com
>> Tested-by: syzbot+f7af59df5d6b25f0febd@syzkaller.appspotmail.com
>> Fixes: 171bf93ce11f ("ocfs2: Periodic quota syncing")
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Joseph Qi <joseph.qi@linux.alibaba.com>
>> ---
>> fs/ocfs2/quota_local.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/fs/ocfs2/quota_local.c b/fs/ocfs2/quota_local.c
>> index 8ce462c64c51..ebe0dbc8db4a 100644
>> --- a/fs/ocfs2/quota_local.c
>> +++ b/fs/ocfs2/quota_local.c
>> @@ -782,6 +782,7 @@ static int ocfs2_local_read_info(struct super_block *sb, int type)
>> if (locked)
>> ocfs2_inode_unlock(lqinode, 1);
>> ocfs2_release_local_quota_bitmaps(&oinfo->dqi_chunk);
>> + cancel_delayed_work_sync(&oinfo->dqi_sync_work);
>> kfree(oinfo);
>> }
>> brelse(bh);
>
> In my view, there is one problem:
> If ocfs2_global_read_info() returns error before ->dqi_sync_work is
> initialized, above code will trigger wild pointer error.
>
You're right. Will update and send v2.
Thanks,
Joseph
prev parent reply other threads:[~2024-09-04 3:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 2:09 Joseph Qi
2024-09-04 2:56 ` Heming Zhao
2024-09-04 3:27 ` Joseph Qi [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=e1496ade-7505-47bb-ac96-4dd48e2e530f@linux.alibaba.com \
--to=joseph.qi@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=heming.zhao@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ocfs2-devel@lists.linux.dev \
--cc=syzbot+f7af59df5d6b25f0febd@syzkaller.appspotmail.com \
/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®