From: Thierry Reding <thierry.reding@gmail.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: daniel.vetter@ffwll.ch, emil.l.velikov@gmail.com,
dri-devel@lists.freedesktop.org, john.chehab@intel.com,
fei.jiang@intel.com, intel-gfx@lists.freedesktop.org
Subject: Re: [RFC PATCH v3 4/4] tests/drv_module_reload: add ipvr support
Date: Mon, 24 Nov 2014 10:55:46 +0100 [thread overview]
Message-ID: <20141124095544.GA25912@ulmo.nvidia.com> (raw)
In-Reply-To: <20141121203633.GB25711@phenom.ffwll.local>
[-- Attachment #1.1: Type: text/plain, Size: 1409 bytes --]
On Fri, Nov 21, 2014 at 09:36:33PM +0100, Daniel Vetter wrote:
> On Fri, Nov 21, 2014 at 09:27:04PM +0100, Thierry Reding wrote:
> > On Sat, Nov 22, 2014 at 03:10:01AM +0800, Yao Cheng wrote:
> > > on vlv, if ipvr is installed, it need be manually unloaded before
> > > i915, otherwise user might run into use-after-free issue.
> >
> > Huh? That doesn't sound right. What exactly is it that's going wrong?
> > You should never have to do this. If you do you're almost certainly
> > doing something wrong in the kernel module.
>
> It's the hilarity called platform devices. Removing them is somewhat racy,
> so doing that upfront makes the entire thing a bit safer. The use after
> free is on the text, since grabbing a module refcount for the platform
> device doesn't work (it would pin the module forever).
I don't understand what the issue is here. I've used platform devices
quite extensively on ARM and I've never encountered a situation where
they were insufficient (or racy for that matter).
If I understand correctly what this commit tries to achieve, then it
unloads one module before another module that it depends on so that the
dependency can be removed subsequently without causing a crash. That
sounds really brittle to me. How are you going to document this for
users so that they don't accidentally go and unload the i915 module and
crash their system?
Thierry
[-- Attachment #1.2: Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2014-11-24 9:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 19:10 [RFC PATCH v3 4/4] tests/drv_module_reload: add ipvr support Yao Cheng
2014-11-21 20:27 ` Thierry Reding
2014-11-21 20:36 ` Daniel Vetter
2014-11-24 9:55 ` Thierry Reding [this message]
2014-11-24 13:14 ` Daniel Vetter
2014-12-01 3:06 ` Cheng, Yao
2014-12-17 8:13 ` Thierry Reding
2014-12-18 5:44 ` Cheng, Yao
2014-12-18 10:04 ` Thierry Reding
2014-12-18 11:21 ` Daniel Vetter
2014-12-21 14:40 ` Cheng, Yao
2015-01-05 8:39 ` Daniel Vetter
2015-01-06 14:14 ` Cheng, Yao
2015-01-07 7:33 ` Daniel Vetter
2014-12-17 8:02 ` Thierry Reding
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=20141124095544.GA25912@ulmo.nvidia.com \
--to=thierry.reding@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=emil.l.velikov@gmail.com \
--cc=fei.jiang@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=john.chehab@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox