- 14 Mar, 2007 19 commits
-
-
Al Viro authored
Signed-off-by:
Al Viro <viro@zeniv.linux.org.uk> Acked-by:
Olof Johansson <olof@lixom.net> Signed-off-by:
Linus Torvalds <torvalds@linux-foundation.org>
-
Al Viro authored
Signed-off-by:
-
Al Viro authored
Signed-off-by:
Jeff Garzik <jgarzik@pobox.com> Signed-off-by:
-
Al Viro authored
Andi had removed a bunch of those, but one more had creeped in... Signed-off-by:
-
Al Viro authored
Signed-off-by:
-
Al Viro authored
Signed-off-by:
-
Al Viro authored
Signed-off-by:
-
Al Viro authored
It's bool and it depends on IDE => should depend on IDE=y Signed-off-by:
-
Al Viro authored
not needed and actually breaks build on frv, while we are at it Signed-off-by:
-
Al Viro authored
... instead of trying to duplicate its bits Signed-off-by:
-
Al Viro authored
method gets u64, not dma_addr_t Signed-off-by:
-
Al Viro authored
and no, it's not the case of "let's pull bits from underlying architecture" Signed-off-by:
-
Al Viro authored
zatm_init() and zatm_start() should be __devinit (the former is not module init, despite the name - it's a helper for PCI ->probe()) Signed-off-by:
Jeff Garzik <jeff@garzik.org> Signed-off-by:
-
Al Viro authored
Signed-off-by:
-
Al Viro authored
PGALLOC_DMA is defined only if we have CONFIG_ZONE_DMA Signed-off-by:
-
Al Viro authored
Signed-off-by:
-
Al Viro authored
used by ->attach() in pcmcia analog Signed-off-by:
-
Al Viro authored
have it return the buffer it had allocated Acked-by:
Stephen Smalley <sds@tycho.nsa.gov> Acked-by:
James Morris <jmorris@namei.org> Signed-off-by:
-
Al Viro authored
GFP_KERNEL allocations in non-blocking context; fixed by killing an idiotic use of security_getprocattr(). Acked-by:
-
- 13 Mar, 2007 14 commits
-
-
Linus Torvalds authored
* master.kernel.org:/pub/scm/linux/kernel/git/davem/sparc-2.6: [SPARC64]: Add missing HPAGE_MASK masks on address parameters. [SPARC]: Hook up missing syscalls.
-
git://ftp.linux-mips.org/pub/scm/upstream-linusLinus Torvalds authored
* 'upstream' of git://ftp.linux-mips.org/pub/scm/upstream-linus: [MIPS] kspd: ioctl needs a translation entry. [MIPS] Viper2: Remove defective support. [MIPS] Oprofile: Reset all performance registers for MIPS_MT_SMP configs
-
Ralf Baechle authored
Signed-off-by:Ralf Baechle <ralf@linux-mips.org>
-
Ralf Baechle authored
A defconfig file and the 10 lines of code (including comments ...) that are rotting since lmo commit 6516a42dc8b40c6c00010346dd51496125b16644 don't quite make proper support, so let's trash it. Signed-off-by: -
Chris Dearman authored
Signed-off-by:
Chris Dearman <chris@mips.com> Signed-off-by:
-
David S. Miller authored
These pte loops all assume the passed in address is HPAGE aligned, make sure that is actually true. Signed-off-by:David S. Miller <davem@davemloft.net>
-
David S. Miller authored
sys_mbind sys_get_mempolicy sys_set_mempolicy sys_kexec_load sys_move_pages sys_getcpu sys_epoll_pwait This work is largely a result of David Woodhouse's most excellent missing syscalls patch. Signed-off-by: -
Linus Torvalds authored
* 'merge' of master.kernel.org:/pub/scm/linux/kernel/git/paulus/powerpc: [POWERPC] sys_move_pages should be callable from an SPU [POWERPC] Wire up sys_epoll_pwait [POWERPC] Allocate syscall number for sys_getcpu [POWERPC] update cell_defconfig [POWERPC] ps3: always make sure were running on a PS3 [POWERPC] Fix spu SLB invalidations [POWERPC] avoid SPU_ACTIVATE_NOWAKE optimization [POWERPC] spufs: fix possible memory corruption is spufs_mem_write
-
Linus Torvalds authored
* master.kernel.org:/pub/scm/linux/kernel/git/davem/sparc-2.6: [SPARC]: Fix TIF_USEDFPU flag atomicity [SPARC64]: Fix atomicity of TIF update in flush_thread() [BW2]: Fix section mismatch warnings. [CG14]: Fix section mismatch warnings. [SPARC]: We do not need OLD_GETRLIMIT.
-
Linus Torvalds authored
* master.kernel.org:/pub/scm/linux/kernel/git/davem/net-2.6: [XFRM]: Fix missing protocol comparison of larval SAs. [WANROUTER]: Delete superfluous source file "net/wanrouter/af_wanpipe.c". [IPV4]: Fix warning in ip_mc_rejoin_group. [ROSE]: Socket locking is a great invention. [ROSE]: Remove ourselves from waitqueue when receiving a signal [NetLabel]: parse the CIPSO ranged tag on incoming packets
-
Joy Latten authored
I noticed that in xfrm_state_add we look for the larval SA in a few places without checking for protocol match. So when using both AH and ESP, whichever one gets added first, deletes the larval SA. It seems AH always gets added first and ESP is always the larval SA's protocol since the xfrm->tmpl has it first. Thus causing the additional km_query() Adding the check eliminates accidental double SA creation. Signed-off-by:
Joy Latten <latten@austin.ibm.com> Signed-off-by:
-
William Lee Irwin III authored
From: William Lee Irwin III <wli@holomorphy.com> Signed-off-by: -
Robert P. J. Day authored
Delete the apparently superfluous source file net/wanrouter/af_wanpipe.c. Signed-off-by:
Robert P. J. Day <rpjday@mindspring.com> Signed-off-by:
-
Geert Uytterhoeven authored
Kill warning about unused variable `in_dev' when CONFIG_IP_MULTICAST is not set. Signed-off-by:
Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com> Signed-off-by:
-
- 12 Mar, 2007 7 commits
-
-
Zachary Amsden authored
Some gcc put this function in .init.text because the header didn't match. Signed-off-by: -
Zachary Amsden authored
VMI is broken under COMPAT_VDSO, as Xen and other non hardware assisted hypervisors will be. I have been working on a fix for this which works for older glibcs that panic when the new relocatable VDSO is used. However, I believe at this time that the fix is going to be too radical to consider at this stage in the release of 2.6.21. We don't expect this config option to be turned on by vendors for new distributions, so at this point we are willing to drop support for it when VMI is compiled in, and work on a patch for 2.6.22 which more fully addresses the problem. Signed-off-by:
Zachary Amsden <zach@vmware.com> Acked-by:
Ingo Molnar <mingo@elte.hu> Signed-off-by:
-
Eric W. Biederman authored
Because we do not reserve space for the pci-x and pci-e state in struct pci dev we need to dynamically allocate it. However because we need to support restore being called multiple times after a single save it is never safe to free the buffers we have allocated to hold the state. So this patch modifies the save routines to first check to see if we have already allocated a state buffer before allocating a new one. Then the restore routines are modified to not free the state after restoring it. Simple and it fixes some subtle error path handling bugs, that are hard to test for. Signed-off-by:
Eric W. Biederman <ebiederm@xmission.com> Signed-off-by:
Greg Kroah-Hartman <gregkh@suse.de> Acked-by:
Auke Kok <auke-jan.h.kok@intel.com> Signed-off-by:
-
Eric W. Biederman authored
There are two ways pci_save_state and pci_restore_state are used. As helper functions during suspend/resume, and as helper functions around a hardware reset event. When used as helper functions around a hardware reset event there is no reason to believe the calls will be paired, nor is there a good reason to believe that if we restore the msi state from before the reset that it will match the current msi state. Since arch code may change the msi message without going through the driver, drivers currently do not have enough information to even know when to call pci_save_state to ensure they will have msi state in sync with the other kernel irq reception data structures. It turns out the solution is straight forward, cache the state in the existing msi data structures (not the magic pci saved things) and have the msi code update the cached state each time we write to the hardware. This means we never need to read the hardware to figure out what the hardware state should be. By modifying the caching in this manner we get to remove our save_state routines and only need to provide restore_state routines. The only fields that were at all tricky to regenerate were the msi and msi-x control registers and the way we regenerate them currently is a bit dependent upon assumptions on how we use the allow msi registers to be configured and used making the code a little bit brittle. If we ever change what cases we allow or how we configure the msi bits we can address the fragility then. Signed-off-by:
-
Ralf Baechle authored
Especially if you actually try to do it ;-) Signed-off-by:
-
Ralf Baechle authored
Signed-off-by:
-
Paul Moore authored
Commit 484b3669 added support for the CIPSO ranged categories tag. However, it appears that I made a mistake when rebasing then patch to the latest upstream sources for submission and dropped the part of the patch that actually parses the tag on incoming packets. This patch fixes this mistake by adding the required function call to the cipso_v4_skbuff_getattr() function. I've run this patch over the weekend and have not noticed any problems. Signed-off-by:
Paul Moore <paul.moore@hp.com> Acked-by:
-
