From: Ksenija Stanojevic <ksenija.stanojevic@gmail.com>
To: outreachy-kernel@googlegroups.com
Cc: Ksenija Stanojevic <ksenija.stanojevic@gmail.com>
Subject: [PATCH 0/4] Do not DMA on the stack
Date: Sun, 4 Oct 2015 22:13:02 +0200 [thread overview]
Message-ID: <cover.1443989364.git.ksenija.stanojevic@gmail.com> (raw)
Fix error "doing DMA on the stack" by using kzalloc for buffer
allocation in rtl8192u/r8192U_core.c in the following functions:
write_nic_byte_E()
write_nic_byte()
write_nic_word()
write_nic_dword()
Issue found by smatch.
Signed-off-by: Ksenija Stanojevic <ksenija.stanojevic@gmail.com>
Ksenija Stanojevic (4):
Staging: rtl8192u: Do not DMA on the stack in write_nic_byte_E()
Staging: rtl8192u: Do not DMA on the stack in write_nic_byte()
Staging: rtl8192u: Do not DMA on the stack in write_nic_word()
Staging: rtl8192u: Do not DMA on the stack in write_nic_dword()
drivers/staging/rtl8192u/r8192U_core.c | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
--
1.9.1
next reply other threads:[~2015-10-04 20:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-04 20:13 Ksenija Stanojevic [this message]
2015-10-04 20:14 ` [PATCH 1/4] Staging: rtl8192u: Do not DMA on the stack in write_nic_byte_E() Ksenija Stanojevic
2015-10-05 3:17 ` [Outreachy kernel] " Greg KH
2015-10-05 3:27 ` Ksenija Stanojević
2015-10-04 20:14 ` [PATCH 2/4] Staging: rtl8192u: Do not DMA on the stack in write_nic_byte() Ksenija Stanojevic
2015-10-04 20:14 ` [PATCH 3/4] Staging: rtl8192u: Do not DMA on the stack in write_nic_word() Ksenija Stanojevic
2015-10-04 20:15 ` [PATCH 4/4] Staging: rtl8192u: Do not DMA on the stack in write_nic_dword() Ksenija Stanojevic
2015-10-05 3:27 ` Ksenija Stanojević
2015-10-04 20:39 ` [Outreachy kernel] [PATCH 0/4] Do not DMA on the stack Arnd Bergmann
2015-10-05 5:28 ` Ksenija Stanojević
2015-10-05 6:40 ` Ksenija Stanojević
2015-10-05 6:44 ` Ksenija Stanojević
2015-10-05 6:50 ` Ksenija Stanojević
2015-10-05 8:11 ` Arnd Bergmann
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=cover.1443989364.git.ksenija.stanojevic@gmail.com \
--to=ksenija.stanojevic@gmail.com \
--cc=outreachy-kernel@googlegroups.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 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.