[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACna6rxmOC0h9hOpa=5iWFM1THQ8Q4hCi8MnmqkZJbB_U0PJ0A@mail.gmail.com>
Date: Fri, 28 Nov 2014 23:40:46 +0100
From: Rafał Miłecki <zajec5@...il.com>
To: Nicholas Krause <xerofoify@...il.com>,
Michael Büsch <m@...s.ch>
Cc: Stefano Brivio <stefano.brivio@...imi.it>,
Network Development <netdev@...r.kernel.org>,
"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
b43-dev <b43-dev@...ts.infradead.org>
Subject: Re: [PATCH] drivers:net:wireless: Add mutex locking for function,
b43_op_beacon_set_time in main.c
On 28 November 2014 at 23:16, Nicholas Krause <xerofoify@...il.com> wrote:
> Adds needed mutex lockng of wl->mutex in order to prevent issues with separate threads executing on
> the b43_update_templates function call in the function, b43_op_beacon_set_time at the same time.
For all kind of kernel documentation / descriptions we try to fit 72
chars limit and we really try to avoid exceeding 80 chars.
> @@ -5094,8 +5094,9 @@ static int b43_op_beacon_set_tim(struct ieee80211_hw *hw,
> {
> struct b43_wl *wl = hw_to_b43_wl(hw);
>
> - /* FIXME: add locking */
> + mutex_lock(&wl->mutex);
> b43_update_templates(wl);
> + mutex_unlock(&wl->mutex);
>
> return 0;
> }
Does anyone remember why this simple solution wasn't implemented
earlier? Michael?
Nicholas: did you test it anyhow?
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists