linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Mike Looijmans <mike.looijmans@topic.nl>
Cc: <linux-wireless@vger.kernel.org>, <khoroshilov@ispras.ru>,
	Fariya Fatima <fariyaf@gmail.com>
Subject: Re: Commit "rsi: fix memory leak in rsi_load_ta_instructions()" breaks things
Date: Fri, 24 Jul 2015 11:02:32 +0300	[thread overview]
Message-ID: <87egjyf0fb.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <55B1E2CB.3040908@topic.nl> (Mike Looijmans's message of "Fri, 24 Jul 2015 09:01:31 +0200")

Mike Looijmans <mike.looijmans@topic.nl> writes:

> Regarding this commit:
>
> https://lkml.org/lkml/2014/12/12/709
>
>     rsi: fix memory leak in rsi_load_ta_instructions()
>
>     Memory allocated by kmemdup() in rsi_load_ta_instructions() is leaked.
>     But duplication of firmware data here is useless,
>     so the patch removes kmemdup() at all.
>
>     Found by Linux Driver Verification project (linuxtesting.org).
>
>     Signed-off-by: Alexey Khoroshilov <khoroshilov@ispras.ru>
>     Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
>
> We use this driver for the Redpine Wifi chip on our "florida" board,
> and after this commit it stopped working. Symptom was that the "wlan0"
> device was not created at all. Reverting the commit makes it work
> again.
>
> Apparently, the kmemdup action is needed for something. I suspect the
> DMA controller is still copying the firmware data before the method
> returned.
>
> Having no experience with this part of the kernel, I wasn't able to
> come up with a more constructive solution than just reverting the
> patch.

Hmm, rsi doesn't seem to have an entry in MAINTAINERS? Do we have a
maintainer for this driver? Adding Fariya as the first rsi commiter.

Unless someone has better suggestions I'll just revert the patch.

-- 
Kalle Valo

  reply	other threads:[~2015-07-24  8:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-24  7:01 Commit "rsi: fix memory leak in rsi_load_ta_instructions()" breaks things Mike Looijmans
2015-07-24  8:02 ` Kalle Valo [this message]
2015-07-24  8:39 ` Alexey Khoroshilov
2015-07-24 11:02   ` Mike Looijmans
2015-07-24 11:35     ` Alexey Khoroshilov
2015-07-24 13:42       ` Mike Looijmans
2015-07-24 14:12         ` Kalle Valo
2015-07-24 16:26           ` Alexey Khoroshilov
2015-07-24 16: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=87egjyf0fb.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@codeaurora.org \
    --cc=fariyaf@gmail.com \
    --cc=khoroshilov@ispras.ru \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mike.looijmans@topic.nl \
    /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).