1. 18 7月, 2007 8 次提交
    • J
      usermodehelper: Tidy up waiting · 86313c48
      Jeremy Fitzhardinge 提交于
      Rather than using a tri-state integer for the wait flag in
      call_usermodehelper_exec, define a proper enum, and use that.  I've
      preserved the integer values so that any callers I've missed should
      still work OK.
      Signed-off-by: NJeremy Fitzhardinge <jeremy@xensource.com>
      Cc: James Bottomley <James.Bottomley@HansenPartnership.com>
      Cc: Randy Dunlap <randy.dunlap@oracle.com>
      Cc: Christoph Hellwig <hch@infradead.org>
      Cc: Andi Kleen <ak@suse.de>
      Cc: Paul Mackerras <paulus@samba.org>
      Cc: Johannes Berg <johannes@sipsolutions.net>
      Cc: Ralf Baechle <ralf@linux-mips.org>
      Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>
      Cc: Joel Becker <joel.becker@oracle.com>
      Cc: Tony Luck <tony.luck@intel.com>
      Cc: Kay Sievers <kay.sievers@vrfy.org>
      Cc: Srivatsa Vaddagiri <vatsa@in.ibm.com>
      Cc: Oleg Nesterov <oleg@tv-sign.ru>
      Cc: David Howells <dhowells@redhat.com>
      86313c48
    • J
      drivers/*: mark variables with uninitialized_var() · a6343afb
      Jeff Garzik 提交于
      Mark variables in drivers/* with uninitialized_var() if such a warning
      appears, and analysis proves that the var is initialized properly on all
      paths it is used.
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      a6343afb
    • J
      drivers/net/wan/sbni: kill uninit'd var warning · e5fb4f42
      Jeff Garzik 提交于
      It's actually convenient in the code to initialize this and a sister
      variable to zero.
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      e5fb4f42
    • J
      drivers/net/wan/pc300_drv: fix bug caught by gcc warning · 79c63e19
      Jeff Garzik 提交于
      The warning
      
      drivers/net/wan/pc300_drv.c: In function ‘cpc_open’:
      drivers/net/wan/pc300_drv.c:2942: warning: ‘br’ may be used
      uninitialized in this function
      
      was valid.  Ensure 'br' is initialized in all cases.
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      79c63e19
    • J
    • J
      [netdrvr] natsemi: Fix device removal bug · f6c42865
      Jeff Garzik 提交于
      This episode illustrates how an overused warning can train people to
      ignore that warning, which winds up hiding bugs.
      
      The warning
      
      drivers/net/natsemi.c: In function ‘natsemi_remove1’:
      drivers/net/natsemi.c:3222: warning: ignoring return value of
      ‘device_create_file’, declared with attribute warn_unused_result
      
      is oft-ignored, even though at close inspection one notices this occurs
      in the /remove/ function, not normally where creation occurs.  A quick
      s/create/remove/ and we are fixed, with the warning gone.
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      f6c42865
    • A
      atl1: missing include · d3676756
      Al Viro 提交于
      Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      d3676756
    • R
      Freezer: make kernel threads nonfreezable by default · 83144186
      Rafael J. Wysocki 提交于
      Currently, the freezer treats all tasks as freezable, except for the kernel
      threads that explicitly set the PF_NOFREEZE flag for themselves.  This
      approach is problematic, since it requires every kernel thread to either
      set PF_NOFREEZE explicitly, or call try_to_freeze(), even if it doesn't
      care for the freezing of tasks at all.
      
      It seems better to only require the kernel threads that want to or need to
      be frozen to use some freezer-related code and to remove any
      freezer-related code from the other (nonfreezable) kernel threads, which is
      done in this patch.
      
      The patch causes all kernel threads to be nonfreezable by default (ie.  to
      have PF_NOFREEZE set by default) and introduces the set_freezable()
      function that should be called by the freezable kernel threads in order to
      unset PF_NOFREEZE.  It also makes all of the currently freezable kernel
      threads call set_freezable(), so it shouldn't cause any (intentional)
      change of behaviour to appear.  Additionally, it updates documentation to
      describe the freezing of tasks more accurately.
      
      [akpm@linux-foundation.org: build fixes]
      Signed-off-by: NRafael J. Wysocki <rjw@sisk.pl>
      Acked-by: NNigel Cunningham <nigel@nigel.suspend2.net>
      Cc: Pavel Machek <pavel@ucw.cz>
      Cc: Oleg Nesterov <oleg@tv-sign.ru>
      Cc: Gautham R Shenoy <ego@in.ibm.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      83144186
  2. 17 7月, 2007 18 次提交
  3. 16 7月, 2007 6 次提交
  4. 15 7月, 2007 2 次提交
  5. 13 7月, 2007 3 次提交
  6. 12 7月, 2007 3 次提交