From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Dmitry Kandybka <d.kandybka@gmail.com>
Cc: linux-wireless@vger.kernel.org, Dmitry Antipov <dmantipov@yandex.ru>
Subject: Re: [PATCH] wifi: ath9k: fix possible integer overflow in ath9k_get_et_stats()
Date: Tue, 30 Jul 2024 11:46:30 +0200 [thread overview]
Message-ID: <878qxjp5zd.fsf@toke.dk> (raw)
In-Reply-To: <20240725111743.14422-1-d.kandybka@gmail.com>
Dmitry Kandybka <d.kandybka@gmail.com> writes:
> In 'ath9k_get_et_stats()', promote TX stats counters to 'u64'
> to avoid possible integer overflow. Compile tested only.
>
> Found by Linux Verification Center (linuxtesting.org) with SVACE.
>
> Signed-off-by: Dmitry Kandybka <d.kandybka@gmail.com>
Acked-by: Toke Høiland-Jørgensen <toke@toke.dk>
next prev parent reply other threads:[~2024-07-30 9:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-25 11:17 [PATCH] wifi: ath9k: fix possible integer overflow in ath9k_get_et_stats() Dmitry Kandybka
2024-07-30 9:46 ` Toke Høiland-Jørgensen [this message]
2024-08-01 14:59 ` Kalle Valo
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=878qxjp5zd.fsf@toke.dk \
--to=toke@toke.dk \
--cc=d.kandybka@gmail.com \
--cc=dmantipov@yandex.ru \
--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).