All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Ksenija Stanojevic <ksenija.stanojevic@gmail.com>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH 1/4] Staging: rtl8192u: Do not DMA on the stack in write_nic_byte_E()
Date: Mon, 5 Oct 2015 04:17:46 +0100	[thread overview]
Message-ID: <20151005031746.GD27303@kroah.com> (raw)
In-Reply-To: <594338659176808944f42cc535049b9f401c64d7.1443989364.git.ksenija.stanojevic@gmail.com>

On Sun, Oct 04, 2015 at 10:14:00PM +0200, Ksenija Stanojevic wrote:
> Fix error "doing DMA on the stack" by using kzalloc for buffer
> allocation.
> Issue found by smatch.

What does smatch say after you made your changes and you run it on the
code again?

thanks,

greg k-h


  reply	other threads:[~2015-10-05  3:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-04 20:13 [PATCH 0/4] Do not DMA on the stack Ksenija Stanojevic
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   ` Greg KH [this message]
2015-10-05  3:27     ` [Outreachy kernel] " 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=20151005031746.GD27303@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=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.