From: Mohammed Shafi Shajakhan <mohammed@codeaurora.org>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: Mohammed Shafi Shajakhan <mohammed@qti.qualcomm.com>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
Kalle Valo <kvalo@qca.qualcomm.com>,
"kvalo@codeaurora.org" <kvalo@codeaurora.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] ath10k: Add support for ath10k_sta_statistics support
Date: Thu, 24 Mar 2016 17:31:17 +0530 [thread overview]
Message-ID: <20160324120117.GA30872@atheros-ThinkPad-T61> (raw)
In-Reply-To: <20160317122956.GA30285@atheros-ThinkPad-T61>
Hi Michal / Kalle,
>
> On Thu, Mar 17, 2016 at 12:35:00PM +0100, Michal Kazior wrote:
> > On 17 March 2016 at 12:20, Mohammed Shafi Shajakhan
> > <mohammed@codeaurora.org> wrote:
> > > Hi Michal,
> > >
> > > On Thu, Mar 17, 2016 at 12:12:31PM +0100, Michal Kazior wrote:
> > >> On 17 March 2016 at 11:48, Mohammed Shafi Shajakhan
> > >> <mohammed@qti.qualcomm.com> wrote:
> > >> [...]
> > >> > +void ath10k_sta_statistics(struct ieee80211_hw *hw, struct ieee80211_vif *vif,
> > >> > + struct ieee80211_sta *sta,
> > >> > + struct station_info *sinfo)
> > >> > +{
> > >> > + struct ath10k_sta *arsta = (struct ath10k_sta *)sta->drv_priv;
> > >> > + struct ath10k *ar = arsta->arvif->ar;
> > >> > +
> > >> > + mutex_lock(&ar->conf_mutex);
> > >> > +
> > >> > + if (ar->state != ATH10K_STATE_ON &&
> > >> > + ar->state != ATH10K_STATE_RESTARTED)
> > >> > + goto out;
> > >>
> > >> Do you really need mutex and ar->state check in this function?
> > >>
> > >
> > > [shafi] By default peer stats will be disabled, we are enabling this by debugfs
> > > (hw-restart) so i thought these checks are needed , please advise .. Do you say
> > > they will be never hit
> >
> > Hmm.. I think mac80211 shouldn't call sta_statistics() before
> > sta_state() during recovery (it makes no sense). In practice I think
> > this isn't enforced in which case it's a mac80211 bug.
>
> [shafi] sure i will check this. If the hardware is restarting there should
> be no stations connected and station related info.
[shafi] I did not see any checks in mac80211 to prevent this (may be i missed
something), but i did remove the checks and tested it, could not find warnings, crashes
(or) garbage values, so is it safer to remove (unless we find some issue with
this) ?, please suggest Michal.
i was doing this parallely in two terminals
a) while true
do
cat rx_stats | grep duration -A 2
done
b) /sys/kernel/debug/ieee80211/phy0/ath10k# echo 1 > peer_stats
/sys/kernel/debug/ieee80211/phy0/ath10k# echo 0 > peer_stats
(or)
/sys/kernel/debug/ieee80211/phy0/ath10k# echo hw-restart > simulate_fw_crash
>
> >
> > Anyway, this isn't much of a problem now. You only read out u64 from
> > `arsta` (sta->drv_priv). Even if it's uninitialized/undefined there's
> > no way for you to crash the system (it's not a list, spinlock or any
> > other complex data structure). Worst case userspace will get garbage
> > rx_duration value if it happens to get_station() while hw-restart is
> > ongoing.
>
> [shafi] will check this ..
[shafi] agree though i could not see any checks in mac80211 to prevent
sta_set_sinfo (or check for the station state), i did not see any issues in my
testing
>
> >
> > It'd be good to verify this is actually a problem and - assuming you
> > want to guarantee correct readouts at all times - to fix the problem
> > in mac80211.
> >
> [shafi] ok, sure
[shafi] I really don't have a deeper understanding of mac80211 code,
i need to go through it thoroughly if i need to have checks for this
if they were not already there.
regards,
shafi
prev parent reply other threads:[~2016-03-24 12:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 10:48 [PATCH v2 1/2] ath10k: Add support for ath10k_sta_statistics support Mohammed Shafi Shajakhan
2016-03-17 10:49 ` [PATCH v2 2/2] ath10k: Remove debugfs support for Per STA total rx duration Mohammed Shafi Shajakhan
2016-03-17 11:04 ` [PATCH v2 1/2] ath10k: Add support for ath10k_sta_statistics support kbuild test robot
2016-03-17 11:12 ` Michal Kazior
2016-03-17 11:20 ` Mohammed Shafi Shajakhan
2016-03-17 11:35 ` Michal Kazior
2016-03-17 12:30 ` Mohammed Shafi Shajakhan
2016-03-24 12:01 ` Mohammed Shafi Shajakhan [this message]
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=20160324120117.GA30872@atheros-ThinkPad-T61 \
--to=mohammed@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@codeaurora.org \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=michal.kazior@tieto.com \
--cc=mohammed@qti.qualcomm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox