From: Benjamin Larsson <benjamin@southpole.se>
To: Antti Palosaari <crope@iki.fi>,
Akihiro TSUKADA <tskd08@gmail.com>,
linux-media@vger.kernel.org
Subject: Re: Random memory corruption of fe[1]->dvb pointer
Date: Tue, 02 Dec 2014 12:52:15 +0100 [thread overview]
Message-ID: <547DA7EF.50600@southpole.se> (raw)
In-Reply-To: <547D9B92.8060900@iki.fi>
On 2014-12-02 11:59, Antti Palosaari wrote:
> [...]
>> So the solution is to change rtl2832.c to the I2C model? And does this
>> issue only affect the mn8847x drivers ?
>
> It likely affects some other dvb-usb-v2 drivers too. But not af9035 as
> I fixed it initially there I think.
>
>> If this is the case would a patch that does not free the buffer but
>> leaks the memory be ok ? I can add a todo item and log it in syslog.
>> That would for sure be better then crashing the subsystem and the driver
>> is still in staging for a reason.
>
> Maybe yes, but it does not sound absolute any good. I think you will
> need to set FE pointer NULL after driver is removed.
It is NULL now, that is why it is crashing, or the current code leads to
random corruptions.
> Then unregister frontend will not call members of that struct anymore,
> but leak memory?
Well any solution that does not randomly crash the kernel when unloading
the module is fine by me. My suggestion is to leak the memory and put a
note about it in syslog. But I guess there are only a handful of users
of this driver so maybe leave it as it is right now? It must be fixed
anyway before the driver is moved out of staging.
>
> regards
> Antti
>
MvH
Benjamin Larsson
prev parent reply other threads:[~2014-12-02 11:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-30 23:47 Random memory corruption of fe[1]->dvb pointer Benjamin Larsson
2014-12-01 23:30 ` Benjamin Larsson
2014-12-02 9:47 ` Akihiro TSUKADA
2014-12-02 10:02 ` Antti Palosaari
2014-12-02 10:41 ` Benjamin Larsson
2014-12-02 10:59 ` Antti Palosaari
2014-12-02 11:52 ` Benjamin Larsson [this message]
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=547DA7EF.50600@southpole.se \
--to=benjamin@southpole.se \
--cc=crope@iki.fi \
--cc=linux-media@vger.kernel.org \
--cc=tskd08@gmail.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.