linux-leds.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Locking in LED core really not needed or missing?
@ 2016-01-08 20:31 Heiner Kallweit
  2016-01-10  8:17 ` Jacek Anaszewski
  0 siblings, 1 reply; 2+ messages in thread
From: Heiner Kallweit @ 2016-01-08 20:31 UTC (permalink / raw)
  To: linux-leds; +Cc: Jacek Anaszewski

I'm a little puzzled about the more or less completely missing locking in the LED core.

Let's just take led_timer_function as example.
It modifies led_cdev->flags and led_cdev->brightness from soft irq context
(soft blink timer) w/o locking. Accessing these fields is not guaranteed to be atomic
and the function doesn't even use set_bit etc. for modifying the bitmap.

And brightness_set and other exported functions can even be called from
hard irq context (e.g. by triggers).

This seems to be quite unsafe to me. Just think of a soft or hard irq colliding
with a sysfs access. IMHO it's just due to the fact that these collision scenarios
are relatively unlikely that we don't have problems.
Am I missing something or is this actually an open issue?

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2016-01-10  8:17 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-01-08 20:31 Locking in LED core really not needed or missing? Heiner Kallweit
2016-01-10  8:17 ` Jacek Anaszewski

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).