From: Stephen Hemminger <stephen@networkplumber.org>
To: johannes@sipsolutions.net
Cc: linux-wireless@vger.kernel.org
Subject: Fw: [Bug 195953] New: Possible access to unintended variable in "linux/net/mac80211/sta_info.c" line 2158
Date: Thu, 1 Jun 2017 11:07:01 -0700 [thread overview]
Message-ID: <20170601110701.21dcef2a@xeon-e3> (raw)
Begin forwarded message:
Date: Thu, 01 Jun 2017 06:55:22 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: stephen@networkplumber.org
Subject: [Bug 195953] New: Possible access to unintended variable in "linux/net/mac80211/sta_info.c" line 2158
https://bugzilla.kernel.org/show_bug.cgi?id=195953
Bug ID: 195953
Summary: Possible access to unintended variable in
"linux/net/mac80211/sta_info.c" line 2158
Product: Networking
Version: 2.5
Kernel Version: 4.12-rc3
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Other
Assignee: stephen@networkplumber.org
Reporter: petrum@gmail.com
Regression: No
While experimenting with a CodeSonar plugin we develop, we noticed a
potential issue in file "linux/net/mac80211/sta_info.c" line 2158 function
sta_set_sinfo
sinfo->rx_dropped_misc = sta->rx_stats.dropped;
if (sta->pcpu_rx_stats) {
for_each_possible_cpu(cpu) {
struct ieee80211_sta_rx_stats *cpurxs;
cpurxs = per_cpu_ptr(sta->pcpu_rx_stats, cpu);
/*HERE*/ sinfo->rx_packets += cpurxs->dropped;
}
}
Wasn't the intention to use "rx_dropped_misc" (instead of "rx_packets") in the
indicated line. In the first line, "rx_dropped_misc" is updated.
Thank you.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2017-06-01 18:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 18:07 Stephen Hemminger [this message]
2017-06-01 18:23 ` Fw: [Bug 195953] New: Possible access to unintended variable in "linux/net/mac80211/sta_info.c" line 2158 Johannes Berg
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=20170601110701.21dcef2a@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).