* opp_get_notifier() needs to be under rcu_lock?
@ 2012-11-20 20:08 Kees Cook
0 siblings, 0 replies; 2+ messages in thread
From: Kees Cook @ 2012-11-20 20:08 UTC (permalink / raw)
To: MyungJoo Ham; +Cc: LKML, Serge Hallyn
Hi,
It looks like find_device_opp() (called from opp_get_notifier()) needs
to be under RCU read lock, but this doesn't seem to be happening in
drivers/devfreq/devfreq.c. Doesn't this run the risk of referencing a
freed variable?
Thanks,
-Kees
--
Kees Cook
Chrome OS Security
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: opp_get_notifier() needs to be under rcu_lock?
@ 2012-11-21 9:58 MyungJoo Ham
0 siblings, 0 replies; 2+ messages in thread
From: MyungJoo Ham @ 2012-11-21 9:58 UTC (permalink / raw)
To: Kees Cook; +Cc: LKML, Serge Hallyn
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=euc-kr, Size: 586 bytes --]
> Hi,
>
> It looks like find_device_opp() (called from opp_get_notifier()) needs
> to be under RCU read lock, but this doesn't seem to be happening in
> drivers/devfreq/devfreq.c. Doesn't this run the risk of referencing a
> freed variable?
>
> Thanks,
>
> -Kees
Yes, that's an issue requiring updates.
Thank you for pointing out.
Cheers,
MyungJoo
>
> --
> Kees Cook
> Chrome OS Security
>
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2012-11-21 9:59 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-11-21 9:58 opp_get_notifier() needs to be under rcu_lock? MyungJoo Ham
-- strict thread matches above, loose matches on Subject: below --
2012-11-20 20:08 Kees Cook
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox