[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <97ae3ac2-c0a8-d675-50a4-0daf960c7f05@linux.ibm.com>
Date: Fri, 24 Jun 2022 14:45:37 +0200
From: Laurent Dufour <ldufour@...ux.ibm.com>
To: Christoph Hellwig <hch@...radead.org>
Cc: mpe@...erman.id.au, benh@...nel.crashing.org, paulus@...ba.org,
nathanl@...ux.ibm.com, haren@...ux.vnet.ibm.com, npiggin@...il.com,
linuxppc-dev@...ts.ozlabs.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 2/4] watchdog: export watchdog_mutex and
lockup_detector_reconfigure
On 24/06/2022, 11:37:23, Christoph Hellwig wrote:
> On Tue, Jun 14, 2022 at 03:54:12PM +0200, Laurent Dufour wrote:
>> The watchdog_mutex is exported to allow some variable to be changed under
>> its protection and prevent any conflict.
>> The lockup_detector_reconfigure() function is exported and is expected to
>> be called under the protection of watchdog_mutex.
>
> Please provide an actual function accessor instead of directly touching
> a global lock.
Thanks Christoph,
I'll try to not touch to that mutex, if that's not doable, I'll create
function accessor as you're suggesting.
Powered by blists - more mailing lists