[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1c0f49ac-2634-4126-abcd-7859fc71f134@I-love.SAKURA.ne.jp>
Date: Tue, 24 Jun 2025 10:55:20 +0900
From: Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
To: Heming Zhao <heming.zhao@...e.com>
Cc: LKML <linux-kernel@...r.kernel.org>, Mark Fasheh <mark@...heh.com>,
Joel Becker <jlbec@...lplan.org>,
Joseph Qi <joseph.qi@...ux.alibaba.com>,
jiangyiwen <jiangyiwen@...wei.com>,
Andrew Morton
<akpm@...ux-foundation.org>,
ocfs2-devel@...ts.linux.dev,
Diogo Jahchan Koike <djahchankoike@...il.com>
Subject: Re: [PATCH] ocfs2: kill osb->system_file_mutex lock
On 2025/06/24 10:33, Heming Zhao wrote:
> Hello,
>
> Protecting refcnt with a mutex is the right approach, and commit 43b10a20372d
> did it properly.
> However, I don't see how your patch fixes the syzbot report [1]. Could you
> elaborate on the root cause analysis?
>
> My review comments are inline below.
>
> [1]: https://syzkaller.appspot.com/bug?extid=1fed2de07d8e11a3ec1b
My patch does not fix [1]. My patch fixes a bug which syzbot reported at
https://lkml.kernel.org/r/000000000000ff2d7a0620381afe@google.com
when testing with Diogo's patch at
https://syzkaller.appspot.com/x/patch.diff?x=178f93d5980000 for [1].
>> Reported-by: Diogo Jahchan Koike <djahchankoike@...il.com>
> 'Reported-by' should be: https://syzkaller.appspot.com/bug?extid=1fed2de07d8e11a3ec1b
Since there is not yet a bug link for my patch, I don't choose syzbot as reporter.
Diogo will post a formal patch for fixing [1] after returning from vacation.
Powered by blists - more mailing lists