From: Larry Finger <Larry.Finger@lwfinger.net>
To: Nicholas Krause <xerofoify@gmail.com>
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
b43-dev@lists.infradead.org, kvalo@codeaurora.org,
linux-kernel@vger.kernel.org
Subject: [PATCH] net:wireless:Add proper locking for the function, b43_op_beacon_set_tim in main.c
Date: Sun, 25 Jan 2015 10:51:49 -0600 [thread overview]
Message-ID: <54C51F25.9050602@lwfinger.net> (raw)
In-Reply-To: <1422169574-8451-1-git-send-email-xerofoify@gmail.com>
On 01/25/2015 01:06 AM, Nicholas Krause wrote:
> Adds proper locking for the function, b43_op_beacon_set_tim in main.c that internally calls b43_update_templates.
> Due to the function that is being called internally,b43_update_templates needing the mutex lock of the structure
> pointer wl passed it to run successfully and without issues we add the calls to mutex_lock before and mutex_unlock
> after it's call internally in b43_op_beacon_set_tim in order to allow the function,,b43_update_templates to run
> successfully and without issues related to concurrent access.
>
> Signed-off-by: Nicholas Krause <xerofoify@gmail.com>
> ---
> drivers/net/wireless/b43/main.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/wireless/b43/main.c b/drivers/net/wireless/b43/main.c
> index 47731cb..b807958 100644
> --- a/drivers/net/wireless/b43/main.c
> +++ b/drivers/net/wireless/b43/main.c
> @@ -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;
> }
Nicolas,
You must be an idiot for resubmitting this patch after Michael Busch clearly
told you that this patch can *never* work as we are in atomic context here! If
you are looking for patch credits, submitting one that messes with locking *that
you have never tested* will certainly get you notoriety on the Internet, but I
doubt that you want that bad a reputation!!
NACK.
Larry
WARNING: multiple messages have this Message-ID (diff)
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Nicholas Krause <xerofoify@gmail.com>
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
b43-dev@lists.infradead.org, kvalo@codeaurora.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net:wireless:Add proper locking for the function, b43_op_beacon_set_tim in main.c
Date: Sun, 25 Jan 2015 10:51:49 -0600 [thread overview]
Message-ID: <54C51F25.9050602@lwfinger.net> (raw)
In-Reply-To: <1422169574-8451-1-git-send-email-xerofoify@gmail.com>
On 01/25/2015 01:06 AM, Nicholas Krause wrote:
> Adds proper locking for the function, b43_op_beacon_set_tim in main.c that internally calls b43_update_templates.
> Due to the function that is being called internally,b43_update_templates needing the mutex lock of the structure
> pointer wl passed it to run successfully and without issues we add the calls to mutex_lock before and mutex_unlock
> after it's call internally in b43_op_beacon_set_tim in order to allow the function,,b43_update_templates to run
> successfully and without issues related to concurrent access.
>
> Signed-off-by: Nicholas Krause <xerofoify@gmail.com>
> ---
> drivers/net/wireless/b43/main.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/wireless/b43/main.c b/drivers/net/wireless/b43/main.c
> index 47731cb..b807958 100644
> --- a/drivers/net/wireless/b43/main.c
> +++ b/drivers/net/wireless/b43/main.c
> @@ -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;
> }
Nicolas,
You must be an idiot for resubmitting this patch after Michael Busch clearly
told you that this patch can *never* work as we are in atomic context here! If
you are looking for patch credits, submitting one that messes with locking *that
you have never tested* will certainly get you notoriety on the Internet, but I
doubt that you want that bad a reputation!!
NACK.
Larry
next prev parent reply other threads:[~2015-01-25 16:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-25 7:06 [PATCH] net:wireless:Add proper locking for the function, b43_op_beacon_set_tim in main.c Nicholas Krause
2015-01-25 7:06 ` Nicholas Krause
2015-01-25 8:14 ` Rafał Miłecki
2015-01-25 8:14 ` Rafał Miłecki
2015-01-25 16:51 ` Larry Finger [this message]
2015-01-25 16:51 ` Larry Finger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54C51F25.9050602@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=b43-dev@lists.infradead.org \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=xerofoify@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.