From: Kalle Valo <kvalo@codeaurora.org>
To: Karthikeyan Periyasamy <periyasa@codeaurora.org>
Cc: ath11k@lists.infradead.org
Subject: Re: [PATCH] ath11k: fix invalid memory access
Date: Mon, 24 Jun 2019 10:54:58 +0000 (UTC) [thread overview]
Message-ID: <20190624105458.025FF609D4@smtp.codeaurora.org> (raw)
In-Reply-To: <1561056973-32524-1-git-send-email-periyasa@codeaurora.org>
Karthikeyan Periyasamy <periyasa@codeaurora.org> wrote:
> dp_reo_cache_flush_elem element get dynamically allocated with invalid size
> which leads to the access of unallocated memory region or memory corruption.
> Fix this bug by allocate with dp_reo_cache_flush_elem structure size.
>
> Signed-off-by: Karthikeyan Periyasamy <periyasa@codeaurora.org>
> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
11 patches applied to ath11k-bringup branch of ath.git, thanks.
f1df70c948f4 ath11k: fix invalid memory access
3213345e51fc ath11k: Remove unnecessary whitespaces
9d18a5b1d777 ath11k: Avoid blank lines related warning
e3b79f9ec2a4 ath11k: Avoid space related warning
dcc1fd37c6dd ath11k: Fix Alignment should match open parenthesis warning
d2b20789808d ath11k: Fix misspelled warnings
e4e738f422d4 ath11k: fix unnecessary brace warnings
61bfed886e93 ath11k: fix Block comments warnings
1e9c09edaba3 ath11k: fix SPDX comment style warnings
6a82b2e7f17e ath11k: fix return statements on void function warnings
ff1effad0d9b ath11k: fix string split across warnings
--
https://patchwork.kernel.org/patch/11007773/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next prev parent reply other threads:[~2019-06-24 10:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 18:56 [PATCH] ath11k: fix invalid memory access Karthikeyan Periyasamy
2019-06-24 10:54 ` Kalle Valo [this message]
2019-06-24 11:01 ` 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=20190624105458.025FF609D4@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=periyasa@codeaurora.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.