1. 16 May, 2018 1 commit
  2. 13 Jun, 2017 1 commit
  3. 24 Jan, 2017 1 commit
    • Johannes Berg's avatar
      rfkill: remove rfkill-regulator · 1331b62c
      Johannes Berg authored
      There are no users of this ("vrfkill") in the tree, so it's just
      dead code - remove it.
      
      This also isn't really how rfkill is supposed to be used - it's
      intended as a signalling mechanism to/from the device, which the
      driver (and partially cfg80211) will handle - having a separate
      rfkill instance for a regulator is confusing, the driver should
      use the regulator instead to turn off the device when requested.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      1331b62c
  4. 09 Jan, 2017 1 commit
  5. 20 Dec, 2016 1 commit
  6. 16 Dec, 2016 1 commit
  7. 13 Dec, 2016 3 commits
  8. 05 Apr, 2016 1 commit
  9. 24 Feb, 2016 10 commits
  10. 26 Jan, 2016 1 commit
    • Johannes Berg's avatar
      rfkill: fix rfkill_fop_read wait_event usage · 6736fde9
      Johannes Berg authored
      The code within wait_event_interruptible() is called with
      !TASK_RUNNING, so mustn't call any functions that can sleep,
      like mutex_lock().
      
      Since we re-check the list_empty() in a loop after the wait,
      it's safe to simply use list_empty() without locking.
      
      This bug has existed forever, but was only discovered now
      because all userspace implementations, including the default
      'rfkill' tool, use poll() or select() to get a readable fd
      before attempting to read.
      
      Cc: stable@vger.kernel.org
      Fixes: c64fb016 ("rfkill: create useful userspace interface")
      Reported-by: default avatarDmitry Vyukov <dvyukov@google.com>
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      6736fde9
  11. 04 Jan, 2016 1 commit
  12. 10 Dec, 2015 1 commit
    • Johannes Berg's avatar
      rfkill: copy the name into the rfkill struct · b7bb1100
      Johannes Berg authored
      Some users of rfkill, like NFC and cfg80211, use a dynamic name when
      allocating rfkill, in those cases dev_name(). Therefore, the pointer
      passed to rfkill_alloc() might not be valid forever, I specifically
      found the case that the rfkill name was quite obviously an invalid
      pointer (or at least garbage) when the wiphy had been renamed.
      
      Fix this by making a copy of the rfkill name in rfkill_alloc().
      
      Cc: stable@vger.kernel.org
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      b7bb1100
  13. 04 Sep, 2015 1 commit
  14. 13 Aug, 2015 1 commit
  15. 11 Aug, 2015 1 commit
  16. 29 May, 2015 1 commit
  17. 20 May, 2015 1 commit
  18. 03 Feb, 2015 1 commit
  19. 04 Nov, 2014 1 commit
  20. 20 Oct, 2014 1 commit
  21. 09 Oct, 2014 1 commit
  22. 08 Oct, 2014 1 commit
  23. 22 Sep, 2014 1 commit
  24. 16 Sep, 2014 1 commit
  25. 29 Aug, 2014 1 commit
  26. 25 Aug, 2014 1 commit
  27. 07 May, 2014 1 commit
  28. 11 Apr, 2014 2 commits