1. 12 4月, 2009 1 次提交
  2. 31 3月, 2009 1 次提交
    • A
      proc 2/2: remove struct proc_dir_entry::owner · 99b76233
      Alexey Dobriyan 提交于
      Setting ->owner as done currently (pde->owner = THIS_MODULE) is racy
      as correctly noted at bug #12454. Someone can lookup entry with NULL
      ->owner, thus not pinning enything, and release it later resulting
      in module refcount underflow.
      
      We can keep ->owner and supply it at registration time like ->proc_fops
      and ->data.
      
      But this leaves ->owner as easy-manipulative field (just one C assignment)
      and somebody will forget to unpin previous/pin current module when
      switching ->owner. ->proc_fops is declared as "const" which should give
      some thoughts.
      
      ->read_proc/->write_proc were just fixed to not require ->owner for
      protection.
      
      rmmod'ed directories will be empty and return "." and ".." -- no harm.
      And directories with tricky enough readdir and lookup shouldn't be modular.
      We definitely don't want such modular code.
      
      Removing ->owner will also make PDE smaller.
      
      So, let's nuke it.
      
      Kudos to Jeff Layton for reminding about this, let's say, oversight.
      
      http://bugzilla.kernel.org/show_bug.cgi?id=12454Signed-off-by: NAlexey Dobriyan <adobriyan@gmail.com>
      99b76233
  3. 09 3月, 2009 1 次提交
  4. 30 1月, 2009 1 次提交
    • J
      Input: stop autorepeat timer on key release · e7b5c1ef
      Johannes Berg 提交于
      Whenever you press and then release a key, the CPU wakes up
      three times:
       * press
       * release
       * autorepeat timer exactly 250ms after press
      
      The autorepeat timer has nothing to do, obviously, since you already
      have released the key, so stop it on key release.
      
      [dtor@mail.ru: This changes autorepeat behavior a bit since we now stop
       autorepeat even if key that is being released is not the one that is
       being auto-repeated, but I believe the new behavior is better.]
      Signed-off-by: NJohannes Berg <johannes@sipsolutions.net>
      Signed-off-by: NDmitry Torokhov <dtor@mail.ru>
      e7b5c1ef
  5. 30 10月, 2008 1 次提交
  6. 30 6月, 2008 1 次提交
  7. 21 6月, 2008 1 次提交
  8. 29 4月, 2008 2 次提交
  9. 31 1月, 2008 1 次提交
  10. 21 1月, 2008 2 次提交
  11. 03 1月, 2008 1 次提交
  12. 14 12月, 2007 1 次提交
  13. 20 10月, 2007 1 次提交
  14. 14 10月, 2007 1 次提交
  15. 13 10月, 2007 1 次提交
    • K
      Driver core: change add_uevent_var to use a struct · 7eff2e7a
      Kay Sievers 提交于
      This changes the uevent buffer functions to use a struct instead of a
      long list of parameters. It does no longer require the caller to do the
      proper buffer termination and size accounting, which is currently wrong
      in some places. It fixes a known bug where parts of the uevent
      environment are overwritten because of wrong index calculations.
      
      Many thanks to Mathieu Desnoyers for finding bugs and improving the
      error handling.
      Signed-off-by: NKay Sievers <kay.sievers@vrfy.org>
      Cc: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
      Cc: Cornelia Huck <cornelia.huck@de.ibm.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      
      7eff2e7a
  16. 30 8月, 2007 1 次提交
  17. 18 7月, 2007 1 次提交
  18. 10 7月, 2007 1 次提交
  19. 09 5月, 2007 1 次提交
  20. 25 4月, 2007 1 次提交
  21. 12 4月, 2007 2 次提交
  22. 16 3月, 2007 1 次提交
  23. 15 3月, 2007 1 次提交
  24. 08 3月, 2007 2 次提交
  25. 18 2月, 2007 1 次提交
  26. 15 2月, 2007 1 次提交
    • T
      [PATCH] remove many unneeded #includes of sched.h · cd354f1a
      Tim Schmielau 提交于
      After Al Viro (finally) succeeded in removing the sched.h #include in module.h
      recently, it makes sense again to remove other superfluous sched.h includes.
      There are quite a lot of files which include it but don't actually need
      anything defined in there.  Presumably these includes were once needed for
      macros that used to live in sched.h, but moved to other header files in the
      course of cleaning it up.
      
      To ease the pain, this time I did not fiddle with any header files and only
      removed #includes from .c-files, which tend to cause less trouble.
      
      Compile tested against 2.6.20-rc2 and 2.6.20-rc2-mm2 (with offsets) on alpha,
      arm, i386, ia64, mips, powerpc, and x86_64 with allnoconfig, defconfig,
      allmodconfig, and allyesconfig as well as a few randconfigs on x86_64 and all
      configs in arch/arm/configs on arm.  I also checked that no new warnings were
      introduced by the patch (actually, some warnings are removed that were emitted
      by unnecessarily included header files).
      Signed-off-by: NTim Schmielau <tim@physik3.uni-rostock.de>
      Acked-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      cd354f1a
  27. 13 2月, 2007 1 次提交
  28. 03 11月, 2006 1 次提交
  29. 14 9月, 2006 4 次提交
  30. 11 9月, 2006 1 次提交
  31. 19 7月, 2006 2 次提交
    • A
      Input: implement new force feedback interface · 509ca1a9
      Anssi Hannula 提交于
      Implement a new force feedback interface, in which all non-driver-specific
      operations are separated to a common module. This includes handling effect
      type validations, locking, etc.
      
      The effects are now file descriptor specific instead of the previous strange
      half-process half-fd specific behaviour. The effect memory of devices is not
      emptied if the root user opens and closes the device while another user is
      using effects. This is a minor change and most likely no force feedback
      aware programs are affected by this negatively.
      
      Otherwise the userspace interface is left unaltered.
      Signed-off-by: NAnssi Hannula <anssi.hannula@gmail.com>
      Signed-off-by: NDmitry Torokhov <dtor@mail.ru>
      509ca1a9
    • D
      Input: add missing handler->start() call · b6d786db
      Dmitry Torokhov 提交于
      The start() method need to be called every time we create
      a new handle. This includes not only registering new devices
      but also when registering new handlers.
      Signed-off-by: NDmitry Torokhov <dtor@mail.ru>
      b6d786db
  32. 15 7月, 2006 1 次提交