From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Sujith Manoharan <sujith@msujith.org>
Cc: <ath10k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 2/3] ath10k: Fix locking for WEP keys
Date: Mon, 24 Nov 2014 17:15:38 +0200 [thread overview]
Message-ID: <87h9xo6351.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1416796657-24657-3-git-send-email-sujith@msujith.org> (Sujith Manoharan's message of "Mon, 24 Nov 2014 08:07:36 +0530")
Sujith Manoharan <sujith@msujith.org> writes:
> From: Sujith Manoharan <c_manoha@qca.qualcomm.com>
>
> peer->keys needs to be protected by data_lock
> since it is also accessed from the WMI path.
>
> Both install() and clear() routines for peer
> keys modify the key contents, so use the data_lock
> to avoid races.
>
> Signed-off-by: Sujith Manoharan <c_manoha@qca.qualcomm.com>
Can you also document the field with "protected by data_lock" in core.h?
--
Kalle Valo
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Sujith Manoharan <sujith@msujith.org>
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH 2/3] ath10k: Fix locking for WEP keys
Date: Mon, 24 Nov 2014 17:15:38 +0200 [thread overview]
Message-ID: <87h9xo6351.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1416796657-24657-3-git-send-email-sujith@msujith.org> (Sujith Manoharan's message of "Mon, 24 Nov 2014 08:07:36 +0530")
Sujith Manoharan <sujith@msujith.org> writes:
> From: Sujith Manoharan <c_manoha@qca.qualcomm.com>
>
> peer->keys needs to be protected by data_lock
> since it is also accessed from the WMI path.
>
> Both install() and clear() routines for peer
> keys modify the key contents, so use the data_lock
> to avoid races.
>
> Signed-off-by: Sujith Manoharan <c_manoha@qca.qualcomm.com>
Can you also document the field with "protected by data_lock" in core.h?
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2014-11-24 15:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 2:37 [PATCH 0/3] ath10k patches Sujith Manoharan
2014-11-24 2:37 ` Sujith Manoharan
2014-11-24 2:37 ` [PATCH 1/3] ath10k: Fix shared WEP Sujith Manoharan
2014-11-24 2:37 ` Sujith Manoharan
2014-11-24 15:12 ` Kalle Valo
2014-11-24 15:12 ` Kalle Valo
2014-11-25 5:28 ` Sujith Manoharan
2014-11-25 5:28 ` Sujith Manoharan
2014-11-25 5:53 ` Kalle Valo
2014-11-25 5:53 ` Kalle Valo
2014-11-24 2:37 ` [PATCH 2/3] ath10k: Fix locking for WEP keys Sujith Manoharan
2014-11-24 2:37 ` Sujith Manoharan
2014-11-24 15:15 ` Kalle Valo [this message]
2014-11-24 15:15 ` Kalle Valo
2014-11-24 2:37 ` [PATCH 3/3] ath10k: Fix bug reported by lockdep Sujith Manoharan
2014-11-24 2:37 ` Sujith Manoharan
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=87h9xo6351.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sujith@msujith.org \
/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.