1. 16 9月, 2009 2 次提交
  2. 11 9月, 2009 4 次提交
  3. 10 9月, 2009 4 次提交
  4. 09 9月, 2009 1 次提交
    • L
      wireless: mark prism54 as deprecated and mark for removal · 4d8cd268
      Luis R. Rodriguez 提交于
      The preferred module is p54pci which also supports FullMAC
      PCI / Cardbus devices. We schedule removal for 2.6.34. Reason
      to remove this is no one really is testing prism54 anymore,
      and while it works p54pci provides support for the same hardware.
      It should be noted I have been told some FullMAC devices may not
      have worked with the SoftMAC driver but to date we have yet to
      recieve a single bug report regarding this. If there are users
      out there please let us know!
      
      Cc: aquilaver@yahoo.com
      Cc: linux-kernel@vger.kernel.org
      Cc: Dan Williams <dcbw@redhat.com>
      Cc: Kai Engert <kengert@redhat.com>
      Cc: Jean Tourrilhes <jt@hpl.hp.com>
      Cc: Tim de Waal<tim.dewaal@yahoo.com>
      Cc: Roy Marples <uberlord@gentoo.org>
      Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
      Cc: Christian Lamparter <chunkeey@web.de>
      Cc: Björn Steinbrink <B.Steinbrink@gmx.de>
      Cc: Tim Gardner <tim.gardner@canonical.com>
      Cc: Larry Finger <Larry.Finger@lwfinger.net>
      Cc: Johannes Berg <johannes@sipsolutions.net>
      Signed-off-by: NLuis R. Rodriguez <lrodriguez@atheros.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      4d8cd268
  5. 08 9月, 2009 1 次提交
    • L
      kmemleak: add clear command support · 30b37101
      Luis R. Rodriguez 提交于
      In an ideal world your kmemleak output will be small, when its
      not (usually during initial bootup) you can use the clear command
      to ingore previously reported and unreferenced kmemleak objects. We
      do this by painting all currently reported unreferenced objects grey.
      We paint them grey instead of black to allow future scans on the same
      objects as such objects could still potentially reference newly
      allocated objects in the future.
      
      To test a critical section on demand with a clean
      /sys/kernel/debug/kmemleak you can do:
      
      echo clear > /sys/kernel/debug/kmemleak
              test your kernel or modules
      echo scan > /sys/kernel/debug/kmemleak
      
      Then as usual to get your report with:
      
      cat /sys/kernel/debug/kmemleak
      Signed-off-by: NLuis R. Rodriguez <lrodriguez@atheros.com>
      Signed-off-by: NCatalin Marinas <catalin.marinas@arm.com>
      30b37101
  6. 07 9月, 2009 2 次提交
    • T
      ALSA: dummy - Fake buffer allocations · a68c4d11
      Takashi Iwai 提交于
      Instead of allocating the real buffers, use a fake buffer and ignore
      read/write in the dummy driver so that we can save the resources.
      For mmap, a single page (unique to the direction, though) is reused
      to all buffers.
      
      When the app requires to read/write the real buffers, pass fake_buffer=0
      module option at loading time.  This will get back to the old behavior.
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      a68c4d11
    • D
      ALSA: hda/realtek: Added support for CLEVO M540R subsystem, 6 channel + digital · a65cc60f
      ddiaz@cenditel.gob.ve 提交于
      The model clevo-m540r was created with 6-channel and digital support. All
      functions verified except spdif. Tested with a VIT D2000 laptop which has:
      
      [lspci extract]
       Audio device [0403]: Intel Corporation 82801H (ICH8 Family) HD Audio
      Controller [8086:284b] (rev 03)
              Subsystem: CLEVO/KAPOK Computer Device [1558:5409]
      
      [/proc/asound/card0/codec\#0 header]
      Codec: Realtek ALC883
      Address: 0
      Function Id: 0x1
      Vendor Id: 0x10ec0883
      Subsystem Id: 0x15585409
      Revision Id: 0x100002
      
      [Added a comment about HP mute and the model description by tiwai]
      Signed-off-by: NDhionel Diaz <ddiaz@cenditel.gob.ve>
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      a65cc60f
  7. 05 9月, 2009 2 次提交
    • B
      sctp: Sysctl configuration for IPv4 Address Scoping · 72388433
      Bhaskar Dutta 提交于
      This patch introduces a new sysctl option to make IPv4 Address Scoping
      configurable <draft-stewart-tsvwg-sctp-ipv4-00.txt>.
      
      In networking environments where DNAT rules in iptables prerouting
      chains convert destination IP's to link-local/private IP addresses,
      SCTP connections fail to establish as the INIT chunk is dropped by the
      kernel due to address scope match failure.
      For example to support overlapping IP addresses (same IP address with
      different vlan id) a Layer-5 application listens on link local IP's,
      and there is a DNAT rule that maps the destination IP to a link local
      IP. Such applications never get the SCTP INIT if the address-scoping
      draft is strictly followed.
      
      This sysctl configuration allows SCTP to function in such
      unconventional networking environments.
      
      Sysctl options:
      0 - Disable IPv4 address scoping draft altogether
      1 - Enable IPv4 address scoping (default, current behavior)
      2 - Enable address scoping but allow IPv4 private addresses in init/init-ack
      3 - Enable address scoping but allow IPv4 link local address in init/init-ack
      Signed-off-by: NBhaskar Dutta <bhaskar.dutta@globallogic.com>
      Signed-off-by: NVlad Yasevich <vladislav.yasevich@hp.com>
      72388433
    • A
      tracing: Remove mentioning of legacy latency_trace file from documentation · 4a88d44a
      Albin Tonnerre 提交于
      The latency_trace file got removed a while back by commit
      886b5b73 and has been replaced
      by the latency-format option.
      
      This patch fixes the documentation by reflecting this change.
      
      Changes since v1:
       - mention that the trace format is configurable through the
         latency-format option
       - Fix a couple mistakes related to the timestamps
      Signed-off-by: NAlbin Tonnerre <albin.tonnerre@free-electrons.com>
      Cc: Steven Rostedt <rostedt@goodmis.org>
      LKML-Reference: <20090831204007.GE4237@pc-ras4041.res.insa>
      Signed-off-by: NFrederic Weisbecker <fweisbec@gmail.com>
      4a88d44a
  8. 03 9月, 2009 1 次提交
  9. 02 9月, 2009 5 次提交
    • D
      KEYS: Add a keyctl to install a process's session keyring on its parent [try #6] · ee18d64c
      David Howells 提交于
      Add a keyctl to install a process's session keyring onto its parent.  This
      replaces the parent's session keyring.  Because the COW credential code does
      not permit one process to change another process's credentials directly, the
      change is deferred until userspace next starts executing again.  Normally this
      will be after a wait*() syscall.
      
      To support this, three new security hooks have been provided:
      cred_alloc_blank() to allocate unset security creds, cred_transfer() to fill in
      the blank security creds and key_session_to_parent() - which asks the LSM if
      the process may replace its parent's session keyring.
      
      The replacement may only happen if the process has the same ownership details
      as its parent, and the process has LINK permission on the session keyring, and
      the session keyring is owned by the process, and the LSM permits it.
      
      Note that this requires alteration to each architecture's notify_resume path.
      This has been done for all arches barring blackfin, m68k* and xtensa, all of
      which need assembly alteration to support TIF_NOTIFY_RESUME.  This allows the
      replacement to be performed at the point the parent process resumes userspace
      execution.
      
      This allows the userspace AFS pioctl emulation to fully emulate newpag() and
      the VIOCSETTOK and VIOCSETTOK2 pioctls, all of which require the ability to
      alter the parent process's PAG membership.  However, since kAFS doesn't use
      PAGs per se, but rather dumps the keys into the session keyring, the session
      keyring of the parent must be replaced if, for example, VIOCSETTOK is passed
      the newpag flag.
      
      This can be tested with the following program:
      
      	#include <stdio.h>
      	#include <stdlib.h>
      	#include <keyutils.h>
      
      	#define KEYCTL_SESSION_TO_PARENT	18
      
      	#define OSERROR(X, S) do { if ((long)(X) == -1) { perror(S); exit(1); } } while(0)
      
      	int main(int argc, char **argv)
      	{
      		key_serial_t keyring, key;
      		long ret;
      
      		keyring = keyctl_join_session_keyring(argv[1]);
      		OSERROR(keyring, "keyctl_join_session_keyring");
      
      		key = add_key("user", "a", "b", 1, keyring);
      		OSERROR(key, "add_key");
      
      		ret = keyctl(KEYCTL_SESSION_TO_PARENT);
      		OSERROR(ret, "KEYCTL_SESSION_TO_PARENT");
      
      		return 0;
      	}
      
      Compiled and linked with -lkeyutils, you should see something like:
      
      	[dhowells@andromeda ~]$ keyctl show
      	Session Keyring
      	       -3 --alswrv   4043  4043  keyring: _ses
      	355907932 --alswrv   4043    -1   \_ keyring: _uid.4043
      	[dhowells@andromeda ~]$ /tmp/newpag
      	[dhowells@andromeda ~]$ keyctl show
      	Session Keyring
      	       -3 --alswrv   4043  4043  keyring: _ses
      	1055658746 --alswrv   4043  4043   \_ user: a
      	[dhowells@andromeda ~]$ /tmp/newpag hello
      	[dhowells@andromeda ~]$ keyctl show
      	Session Keyring
      	       -3 --alswrv   4043  4043  keyring: hello
      	340417692 --alswrv   4043  4043   \_ user: a
      
      Where the test program creates a new session keyring, sticks a user key named
      'a' into it and then installs it on its parent.
      Signed-off-by: NDavid Howells <dhowells@redhat.com>
      Signed-off-by: NJames Morris <jmorris@namei.org>
      ee18d64c
    • D
      KEYS: Add garbage collection for dead, revoked and expired keys. [try #6] · 5d135440
      David Howells 提交于
      Add garbage collection for dead, revoked and expired keys.  This involved
      erasing all links to such keys from keyrings that point to them.  At that
      point, the key will be deleted in the normal manner.
      
      Keyrings from which garbage collection occurs are shrunk and their quota
      consumption reduced as appropriate.
      
      Dead keys (for which the key type has been removed) will be garbage collected
      immediately.
      
      Revoked and expired keys will hang around for a number of seconds, as set in
      /proc/sys/kernel/keys/gc_delay before being automatically removed.  The default
      is 5 minutes.
      Signed-off-by: NDavid Howells <dhowells@redhat.com>
      Signed-off-by: NJames Morris <jmorris@namei.org>
      5d135440
    • T
      ALSA: hda - Add support of Alienware M17x laptop · 842ae638
      Takashi Iwai 提交于
      Added the quirk for Alienware M17x with IDT 92HD73* codec chip.
      It has two HP and one line-out jack, one mic jack, a built-in
      speaker and a built-in mic.
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      842ae638
    • D
      RTO connection timeout: sysctl documentation update · 5d789229
      Damian Lukowski 提交于
      This patch updates the sysctl documentation concerning the interpretation
      of tcp_retries{1,2} and tcp_orphan_retries.
      Signed-off-by: NDamian Lukowski <damian@tvk.rwth-aachen.de>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      5d789229
    • T
      libata: remove spindown skipping and warning · 051d9fbd
      Tejun Heo 提交于
      This was a hack to give userland shutdown tools time to drop manual
      spindown.  All popular distros updated quite some time ago and the due
      is well passed.  Drop it.
      Signed-off-by: NTejun Heo <tj@kernel.org>
      Cc: Jaswinder Singh Rajput <jaswinder@kernel.org>
      Signed-off-by: NJeff Garzik <jgarzik@redhat.com>
      051d9fbd
  10. 01 9月, 2009 1 次提交
  11. 27 8月, 2009 2 次提交
    • T
      ALSA: Add debug module option · 36ce99c1
      Takashi Iwai 提交于
      Add debug module option to snd core.
      This controls the debug print level.  When CONFIG_SND_DEBUG_VERBOSE
      is set, you can suppress the debug messages by giving or changing this
      parameter to a lower value.  debug=0 means no debug messsages.
      As default, it's set to the verbose level 2.
      
      Since this option can be changed dynamically via sysfs file, you can
      suppress the verbose debug messages on the fly, which wasn't possible
      before.
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      36ce99c1
    • C
      kmemleak: Dump object information on request · 189d84ed
      Catalin Marinas 提交于
      By writing dump=<addr> to the kmemleak file, kmemleak will look up an
      object with that address and dump the information it has about it to
      syslog. This is useful in debugging memory leaks.
      Signed-off-by: NCatalin Marinas <catalin.marinas@arm.com>
      189d84ed
  12. 26 8月, 2009 2 次提交
    • J
      tracing: Add vim script to enable folding for function_graph traces · 6591b493
      Josh Triplett 提交于
      function_graph traces look like nested function calls, complete with
      braces denoting the start and end of functions.  function-graph-fold.vim
      teaches vim how to fold these functions, to make it more convenient to
      browse them.
      
      To use, :source function-graph-fold.vim while viewing a function_graph
      trace, or use "view -S function-graph-fold.vim some-trace" to load it
      from the command-line together with a trace.  You can then use the usual
      vim fold commands, such as "za", to open and close nested functions.
      While closed, a fold will show the total time taken for a call, as would
      normally appear on the line with the closing brace.  Folded functions
      will not include finish_task_switch(), so folding should remain
      relatively sane even through a context switch.
      
      Note that this will almost certainly only work well with a single-CPU
      trace (e.g. trace-cmd report --cpu 1).  It also takes some time to run
      (a few seconds for a large trace on my laptop).  Nevertheless, I found
      it very handy to get an overview of a trace and then drill down on
      problematic calls.
      Signed-off-by: NJosh Triplett <josh@joshtriplett.org>
      LKML-Reference: <20090806145701.GB7661@feather>
      Signed-off-by: NSteven Rostedt <rostedt@goodmis.org>
      6591b493
    • T
      ALSA: hda - Add / fix model entries for HD-audio driver · e2e46569
      Takashi Iwai 提交于
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      e2e46569
  13. 23 8月, 2009 4 次提交
  14. 20 8月, 2009 4 次提交
  15. 19 8月, 2009 1 次提交
    • K
      mm: revert "oom: move oom_adj value" · 0753ba01
      KOSAKI Motohiro 提交于
      The commit 2ff05b2b (oom: move oom_adj value) moveed the oom_adj value to
      the mm_struct.  It was a very good first step for sanitize OOM.
      
      However Paul Menage reported the commit makes regression to his job
      scheduler.  Current OOM logic can kill OOM_DISABLED process.
      
      Why? His program has the code of similar to the following.
      
      	...
      	set_oom_adj(OOM_DISABLE); /* The job scheduler never killed by oom */
      	...
      	if (vfork() == 0) {
      		set_oom_adj(0); /* Invoked child can be killed */
      		execve("foo-bar-cmd");
      	}
      	....
      
      vfork() parent and child are shared the same mm_struct.  then above
      set_oom_adj(0) doesn't only change oom_adj for vfork() child, it's also
      change oom_adj for vfork() parent.  Then, vfork() parent (job scheduler)
      lost OOM immune and it was killed.
      
      Actually, fork-setting-exec idiom is very frequently used in userland program.
      We must not break this assumption.
      
      Then, this patch revert commit 2ff05b2b and related commit.
      
      Reverted commit list
      ---------------------
      - commit 2ff05b2b (oom: move oom_adj value from task_struct to mm_struct)
      - commit 4d8b9135 (oom: avoid unnecessary mm locking and scanning for OOM_DISABLE)
      - commit 81236810 (oom: only oom kill exiting tasks with attached memory)
      - commit 933b787b (mm: copy over oom_adj value at fork time)
      Signed-off-by: NKOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
      Cc: Paul Menage <menage@google.com>
      Cc: David Rientjes <rientjes@google.com>
      Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
      Cc: Rik van Riel <riel@redhat.com>
      Cc: Linus Torvalds <torvalds@linux-foundation.org>
      Cc: Oleg Nesterov <oleg@redhat.com>
      Cc: Nick Piggin <npiggin@suse.de>
      Cc: Mel Gorman <mel@csn.ul.ie>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      0753ba01
  16. 18 8月, 2009 1 次提交
  17. 17 8月, 2009 1 次提交
  18. 14 8月, 2009 2 次提交