[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YnMj/SY8BhJuebFO@lunn.ch>
Date: Thu, 5 May 2022 03:10:21 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Ansuel Smith <ansuelsmth@...il.com>
Cc: Vivien Didelot <vivien.didelot@...il.com>,
Florian Fainelli <f.fainelli@...il.com>,
Vladimir Oltean <olteanv@...il.com>,
"David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Jonathan Corbet <corbet@....net>, Pavel Machek <pavel@....cz>,
John Crispin <john@...ozen.org>, netdev@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-doc@...r.kernel.org, linux-leds@...r.kernel.org
Subject: Re: [RFC PATCH v6 07/11] leds: trigger: netdev: use mutex instead of
spinlocks
> @@ -400,7 +400,7 @@ static int netdev_trig_notify(struct notifier_block *nb,
>
> cancel_delayed_work_sync(&trigger_data->work);
>
> - spin_lock_bh(&trigger_data->lock);
> + mutex_lock(&trigger_data->lock);
I'm not sure you can convert a spin_lock_bh() in a mutex_lock().
Did you check this? What context is the notifier called in?
Andrew
Powered by blists - more mailing lists