[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <6fd7a4ee0a9001d9cb0995719df5b88bcd56a870.camel@dubeyko.com>
Date: Wed, 28 May 2025 10:18:57 -0700
From: Viacheslav Dubeyko <slava@...eyko.com>
To: 李扬韬 <frank.li@...o.com>,
"glaubitz@...sik.fu-berlin.de" <glaubitz@...sik.fu-berlin.de>, Andrew
Morton <akpm@...ux-foundation.org>, "Ernesto A."
Fernández <ernesto.mnd.fernandez@...il.com>
Cc: "linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
"linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>,
"syzbot+8c0bc9f818702ff75b76@...kaller.appspotmail.com"
<syzbot+8c0bc9f818702ff75b76@...kaller.appspotmail.com>,
"Slava.Dubeyko@....com"
<Slava.Dubeyko@....com>
Subject: Re: 回复: 回复: [PATCH] hfsplus: remove mutex_lock check
in hfsplus_free_extents
On Wed, 2025-05-28 at 17:01 +0000, 李扬韬 wrote:
> Hi Slava,
>
> > Could you please rework the patch comment by means of adding
> > precise explanation of this?
>
> I don't quite get your point. Would you mind adding a comment or
> editing it here? : )
>
I see your point. We need accurately explain here that several threads
could try to lock the shared extents tree. And warning can be triggered
in one thread when another thread has locked the tree. This is the
wrong behavior of the code and we need to remove the warning.
This is what I meant here.
Thanks,
Slava.
Powered by blists - more mailing lists