- 11 Jan, 2005 39 commits
-
-
Domen Puncer authored
No need for an array here. Therefore no need to worry about possible overflows. seq_printf() can handle this. Signed-off-by:
walter harms <wharms@bfs.de> Signed-off-by:
Domen Puncer <domen@coderock.org> Signed-off-by:
Andrew Morton <akpm@osdl.org> Signed-off-by:
Linus Torvalds <torvalds@osdl.org>
-
Domen Puncer authored
proc_pid_wchan() uses a 128-Byte array for something that can change its size via define. Signed-off-by:
-
Steffen Klassert authored
With this the driver supports the ethtool_ops {get,set}_msglvl, {get,set}_settings, get_stats, get_link, and nway_reset. Unlike the first patch, the userspace ioctl functions are protected with spin_lock_irqsave. Furter I moved the spin_lock_bh from the mdio_{read,write} functions to vortex_timer(). All the locks acquire vp->lock now, vp->mdio_lock is not used any more. Signed-off-by:Steffen Klassert <klassert@mathematik.tu-chemnitz.de> Signed-off-by:
-
Hugh Dickins authored
3c59x now uses generic_mii_ioctl, so VORTEX should select MII. Signed-off-by:
Hugh Dickins <hugh@veritas.com> Signed-off-by:
-
Steffen Klassert authored
With this patch the driver makes use of the MII lib helper function generic_mii_ioctl. Patch is tested with the mii-diag tool and a 3c905-TX, 3c905B-TX NIC. Signed-off-by:
-
Steffen Klassert authored
Patch changes the two remaining direct accessing of dev->priv to netdev_priv. Signed-off-by:
-
François Romieu authored
It is possible to remove the device without calling pci_disable_device(). A leak can take place during the init as well. Signed-off-by:
Francois Romieu <romieu@fr.zoreil.com> Signed-off-by:
-
Nathan Bryant authored
The problem is that under the new PCI driver model, cards are required to always restore state and call pci_enable_device() on resume. So the patch changes the driver to do its restore state calls unconditionally (it used to only do them when it was configured for wake-on-lan) and adds a call to pci_enable_device(). Signed-off-by:
-
John W. Linville authored
Add 3c900 Boomerang to list of devices needing EEPROM_RESET Signed-off-by:
John W. Linville <linville@tuxdriver.com> Signed-off-by:
-
John W. Linville authored
Remove the EEPROM_RESET flag for the 3c905B cards. Signed-off-by:
-
John W. Linville authored
Enable reload of EEPROM values in reset at rmmod for cards that need it, similar to old EEPROM_NORESET flag but in reverse. (Most?) 3c905 and (some?) 3c905B cards need an additional bit unmasked in the reset at rmmod or else they don't get reinitialized properly when the driver is reloaded. Signed-of-by:
-
Adrian Bunk authored
InterMezzo was removed in 2.6, so there's no reason for keeping a MAINTAINERS entry. Signed-off-by:
Adrian Bunk <bunk@stusta.de> Signed-off-by:
-
Prasanna Meda authored
Correct double accounting of elf_buflen in read_kcore:get_kcore_size(). Signed-off-by:
Prasanna Meda <pmeda@akamai.com> Signed-off-by:
-
Roland Dreier authored
Export get_sb_pseudo() so that modules can create unmountable pseudo-filesystems cleanly. Signed-off-by:
Roland Dreier <roland@topspin.com> Signed-off-by:
-
Oleg Drokin authored
This patch below is needed to suppress the warning, with more than one indirect block insertion at a time, it is now possible to split indirect items as well and there were reports on lkml from people who seen this warning and were worried about it. To be on the safe side, I consulted with Vladimir Saveliev and he said that the change is safe to do indeed. Signed-off-by:
-
Mike Miller authored
This patch removes support for 2 controllers that were recently cancelled and it adds support for the P600, a cciss based SAS controller due to ship in late March/early April '05. Neither of these controllers have made it to the field. Signed-off-by:
Mike Miller <mike.miller@hp.com> Signed-off-by:
-
Matt Mackall authored
Remove random pool resizing sysctl. It's racy in hard to fix ways and doesn't really warrant fixing. It also only allows adjusting the input pool size so it's either obsolete or incomplete. The default 4kbits (512 bytes) of entropy pool should be more than big enough for all purposes and too small to be a memory concern. This patch removes the resizing code and marks the sysctl read-only. Signed-off-by:
Matt Mackall <mpm@selenic.com> Signed-off-by:
-
Matt Mackall authored
Whitespace cleanups trailing whitespace removal superfluous brace removal Signed-off-by:
-
Christoph Hellwig authored
On Fri, Dec 10, 2004 at 11:04:22AM +1100, Nathan Scott wrote: > The bug# for the write deadlock I mentioned earlier -- 925836. I finally found some time to look at it, and this fix is almost trivial. XFS doesn't need the i_alloc_sem at all, so we should avoid taking it in direct-io.c completely. As a side-effect it makes the code a little bit simpler even. Signed-off-by:
-
Geert Uytterhoeven authored
M68k: Remove nowhere referenced files Signed-off-by:
Geert Uytterhoeven <geert@linux-m68k.org> Signed-off-by:
-
Geert Uytterhoeven authored
MMC_WBSD depends on ISA (needs isa_virt_to_bus()) Signed-off-by:
-
Geert Uytterhoeven authored
M68k: Update defconfigs for 2.6.10 Signed-off-by:
-
Hirokazu Takata authored
We, Linux/M32R project members, decided to change the kernel API/ABI. This modification is not small, but if we don't change it now, perhaps we have no chance to change them hereafter. * Why change the m32r kernel API/ABI? - The m32r port has many old-style syscall interfaces, because we made m32r port refering to the other traditional archs. Some old syscalls are no longer used or can be safely removed by upgrading the GNU C library. - To make the m32r kernel more secure, it is preferable to prevent stack region from being executed. (e.g. stack overflow) * API/ABI changes - include/asm-m32r/unistd.h: Upgrade to the new kernel API. - arch/m32r/entry.S: Minimum update to the new ABI. - Don't use UID16 syscalls. - To make stack noexecutable: 1) Don't use trampoline for signal handlers for kernel space (cf. sparc64): sys_signal: remove. sys_sigaction, sys_rt_sigaction: use glibc's restorer. 2) Don't generate trampoline code by GCC in userspace: Support non-executable stack by the m32r gcc. --> done (for gcc-3.4.3/gcc-4.0) * New userland - This modification does *not* keep backward compatibility. So we have been prepared new userland, based on the new API/ABI. Already, more than 200 new Debian deb binary packages are available on the Linux/M32R site: http://debian.linux-m32r.org/dists/04_ordovician/ (for this new ABI) Signed-off-by:NIIBE Yutaka <gniibe@fsij.org> Signed-off-by:
Hirokazu Takata <takata@linux-m32r.org> Signed-off-by:
-
Barry K. Nathan authored
During resume, my previous patch switches over to the saved swsusp image without suspending all devices first. This patch fixes that oversight, so that the state of the hardware upon resume more closely matches the state it had at suspend time. While my previous patch alone seemed to work fine in my testing, it is not fully correct without this as well. Signed-off-by:
Barry K. Nathan <barryn@pobox.com> Acked-by:
Pavel Machek <pavel@ucw.cz> Signed-off-by:
-
Barry K. Nathan authored
Since at least kernel 2.6.9, if not earlier, swsusp fails to properly suspend and resume all devices. The most notable effect is that resuming fails to properly reconfigure interrupt routers. In 2.6.9 this was obscured by other kernel code, but in 2.6.10 this often causes post-resume APIC errors and near-total failure of some PCI devices (e.g. network, sound and USB controllers). Even in cases where interrupt routing is unaffected, this bug causes other problems. For instance, on one of my systems I have to run "ifdown eth0;ifup eth0" after resume in order to have functional networking, if I do not apply this patch. By itself, this patch is not theoretically complete; my next patch fixes that. However, this patch is the critical one for fixing swsusp's behavior in the real world. Signed-off-by:
-
Pavel Machek authored
Signed-off-by:
-
Pavel Machek authored
This introduces pm_message_t. For now, it is only good for type-safety and sparse checking, but plan is to turn pm_message_t into structure soon. Signed-off-by:
-
Leendert van Doorn authored
The old code cuts off the higher bits in CR4 (such as X86_CR4_OSFXSR, X86_CR4_OSXMMEXCPT). Signed-off-by: leendert@watson.ibm.com Signed-off-by:
-
Alexander Viro authored
Comment on why iounmap is not appropriate in the early-boot legacy ISA region dmi scan. Signed-off-by:
-
David Gibson authored
This patch makes some cleanups to the #defines for various fields in the MMCR0 performance monitor control register. Specifically, the names of a couple of bits are changed so that: a) they are a bit less cumbersomely long and b) they match the names used in the hardware documentation. Signed-off-by:
David Gibson <dwg@au1.ibm.com> Signed-off-by:
-
Olof Johansson authored
In the recent IOMMU cleanup, the new LPAR code assumes that all PHBs must have a dma window assigned to it. On some machines we don't have a window assinged unless there's an adapter in the slot. In other words, a PHB without a ibm,dma-window property is not a bug and must be tolerated. This patch fixes that, and also removes a redundant check for the dma-window being defined. Signed-off-by:
Olof Johansson <olof@austin.ibm.com> Signed-off-by:
-
Serge Hallyn authored
The vm_enough_memory functionality was replicated in three separate places, and not always kept in sync. It also used capable() for authorization checks. This caused any process which ends up checking for this permission to have PF_SUPERPRIV set (inappropriately), and caused poor dependencies between stacked modules, since each LSM was generically asked to moderate capable(CAP_SYS_ADMIN) without knowing why. Signed-off-by:
Serge Hallyn <serue@us.ibm.com> Signed-off-by:
Chris Wright <chrisw@osdl.org> Signed-off-by:
-
Serge Hallyn authored
The following patch splits bprm_apply_creds into two functions, bprm_apply_creds and bprm_post_apply_creds. The latter is called after the task_lock has been dropped. Without this patch, SELinux must drop the task_lock and re-acquire it during apply_creds, making the 'unsafe' flag meaningless to any later security modules. Please apply. Signed-off-by:
Stephen Smalley <sds@epoch.ncsc.mil> Signed-off-by:
-
Chris Wedgwood authored
Recent changes mean nodemask.h is required in places it previously wasn't. Signed-off-by:
Chris Wedgwood <cw@f00f.org> Signed-off-by:
-
Dominik Brodowski authored
Even though these 2.4. interfaces are already gone in Dave Jones' cpufreq bitkeeper tree, here's a patch which properly announces it in Documentation/feature-removal-schedule.txt: Add meaningful content concerning the removal of deprecated interfaces to the cpufreq core. Signed-off-by:
Dominik Brodowski <linux@brodo.de> Signed-off-by:
-
Jan Kara authored
This fixes the entry in the MAINTAINERS file. I guess Marco agrees with such change as he's not doing a maintaince for some time.
-
Adrian Bunk authored
The patch below makes some needlessly global code static. The most interesting part is that dquot_cachep can become static, since it isn't used outside of dquot.c . Signed-off-by:
Jan Kara <jack@suse.cz> Signed-off-by:
-
Roland McGrath authored
When a thread stops for ptrace exit tracing, it cannot be resumed by SIGKILL. Once PF_EXITING is set, SIGKILL will not cause a wakeup from stop (see wants_signal in kernel/signal.c). This patch moves the ptrace stop for exit tracing before the setting of PF_EXITING. Signed-off-by:
Roland McGrath <roland@redhat.com> Signed-off-by:
-
Roland McGrath authored
Upon reevaluation we think it is indeed safe to permit the race between a ptrace call and the traced thread waking up, as long as it will never get back to user mode. This patch makes SIGKILL wake up threads in TASK_TRACED. That alone resolves most of the deadlock issues that became possible with the introduction of TASK_TRACED, getting us back to the killing behavior of 2.6.8 and before. This patch also further cleans up ptrace detaching, so that threads are left in TASK_STOPPED only if a job control stop is actually in effect, and otherwise resume. This removes the past nuisances requiring a SIGCONT to resume a thread even when it had a pending SIGKILL. Signed-off-by:
-
- 10 Jan, 2005 1 commit
-
-
Chris Wright authored
- allow CAP_IPC_LOCK to override mlock rlimit during stack expansion as in all other cases Signed-off-by:
-
