- 27 Aug, 2004 40 commits
-
-
Ryan S. Arnold authored
Here is an HVCS (drivers/char/hvcs.c) patch which fixes the hvcs driver problems with hotplugged vty-server adapters. The current driver handles the adapter index assignment improperly so after a number of device removals and insertions the driver could no longer map a tty->index to a vty-server properly and tty_open() attempts would fail. This patch solves this problem by always assigning the lowest available index to the new adapters and returning an index to the list when the adapter is removed. changelog: drivers/char/hvcs.c =================== -Added hvcs_index_list to manage the lowest available index. -Added four helper functions to manage the list, which include the creation and destruction of the list, the get'ing of the lowest index, and the returning of an index. -Moved free_irq() outside of the hvcs_final_close() function in order to get it out of the spinlock. -Rearranged hvcs_close() to accomodate the previous change. -Removed local CLC_LENGTH define and used HVCS_CLC_LENGTH from arch/ppc64/hvcserver.h instead. -Cleaned up some printks and did some house keeping on the changelog. Documentation/powerpc/hvcs.txt ============================== -Added information on sysfs 'index' attribute added in previous hvcs patch. -Added Q & A section on how to find the proper dev node for a newly added adapter. I think this is the last of the HVCS patches for a while, as all of my oustanding issues have been dealt with. Signed-off-by:
Ryan S. Arnold <rsa@us.ibm.com> Signed-off-by:
Andrew Morton <akpm@osdl.org> Signed-off-by:
Linus Torvalds <torvalds@osdl.org>
-
Yanmin Zhang authored
There is a minor problem in function start_kernel. start_kernel will enable interrupt after calling profile_init. However, before that, function time_init on IA64 platform could enable interrupt. See this call sequence: start_kernel ->time_init ->ia64_init_itm ->register_time_interpolator ->write_seqlock_irq. Signed-off-by:Zhang Yanmin <yanmin.zhang@intel.com> Signed-off-by:
Yao Jun <junx.yao@intel.com> Signed-off-by:
-
Tom 'spot' Callaway authored
Patch to fix typo in bw2.c, added in 2.6.9-rc1. Signed-off-by:
William Irwin <wli@holomorphy.com> Signed-off-by:
-
Tom 'spot' Callaway authored
This patch changes the name of the sparc32 Kconfig menu from "General Setup" to "General Machine Setup", to match the changes committed to most other arches in 2.6.9-rc1. Signed-off-by:
-
Christoph Hellwig authored
We have this patch that adds ftape support for x86_64 and cleans up the alpha support a little. The comments look like Vojtech did the x86_64 part and I guess the alpha bits are from Herbert Xu. Signed-off-by:
-
William Lee Irwin III authored
While trying out compiling of reiser4 on sparc64, ppc64, alpha, and ia64, I discovered that WAITQUEUE_DEBUG is nowhere defined in 2.6.x, and various compiler versions spew copious warnings at #if on it. Convert __SEMAPHORE_INITIALIZER() to C99 initializers while in the area. Signed-off-by:
-
Arun Sharma authored
32 bit compatibility code sometimes needs to copy unaligned data across kernel/user boundary and currently there is no architecture independent API to do it. (1) Introduce new APIs __{get,put}_user_unaligned. These APIs are necessary because the optimal way to copy unaligned data across kernel/user boundary is different on different architectures. Some architectures don't even care about alignment. On some __put_user is faster than __copy_to_user for small sizes. (2) Optimize __{get,put}_user_unaligned for ia64, x86-64, s390, ppc64. (3) Fix compat_filldir64() which is broken on big-endian machines Thanks to Arnd Bergmann <arnd@arndb.de> for his help. Signed-off-by:Gordon Jin <gordon.jin@intel.com> Signed-off-by:
Arun Sharma <arun.sharma@intel.com> Signed-off-by:
-
Bjorn Helgaas authored
Call pci_enable_device() before looking at pci_dev. Also, call pci_disable_device() when releasing the device. Signed-off-by:
Bjorn Helgaas <bjorn.helgaas@hp.com> Signed-off-by:
-
Tim Schmielau authored
It seems a little unsafe to me to have oom killer badness points of type int, when all the underlying objects are unsigned long. I can't immediately think of a case where this matters much, but e.g. a long-running job or daemon on a 64 bit machine might lose it's bonus because of that. Signed-off-by:
Tim Schmielau <tim@physik3.uni-rostock.de> Signed-off-by:
-
Valdis Kletnieks authored
Here's the last of them for 2.6.9-rc1 - two more #if/#ifdef cleanups. Signed-off-by: <valdis.kletnieks@vt.edu> Signed-off-by:
-
Valdis Kletnieks authored
Another few #if/#ifdef cleanups, this time for the PPC architecture. Signed-off-by: <valdis.kletnieks@vt.edu> Signed-off-by:
-
Valdis Kletnieks authored
Another small #if/#ifdef cleanup, to make things safer for compiling with -Wundef Signed-off-by: <valdis.kletnieks@vt.edu> Signed-off-by:
-
Valdis Kletnieks authored
Another small cleanup patch for #if/#ifdef usage. Signed-off-by: <valdis.kletnieks@vt.edu> Signed-off-by:
-
Valdis Kletnieks authored
This patch changes a bunch of '#if CONFIG_PCI' to '#ifdef' instead, to make the kernel source cleaner for compiling with 'gcc -Wundef'. Signed-off-by:
Karsten keil <kkeil@suse.de> Signed-off-by:
-
Steffen Thoss authored
qeth network driver change: - Make qeth devices which are present but not up addressable by snmp ioctls. Signed-off-by:
Martin Schwidefsky <schwidefsky@de.ibm.com> Signed-off-by:
-
Peter Oberparleiter authored
sclp driver changes: - Add reboot notifier to reset the sclp send/receive masks on shutdown. Signed-off-by:
-
Steffen Thoss authored
common i/o layer change: - Correct check in qdio_stop_polling to avoid loosing initiative on the qdio inbound queue. Signed-off-by:
-
Frank Pavlic authored
lcs network driver changes: - Allocate the reply structure instead of taking it from the stack. - Use del_timer_sync instead of del_timer. - Clean up helper threads creation/shutdown. - Split lcs_register_mc_addresses to make it readable again. - Free multicast list entries when device is going down. - Retransmit multicast list in device recovery. Signed-off-by:
-
Thomas Richter authored
Add support for netmos devices to the parallel port driver. NetMOS 9805 support is already in the kernel, this patch adds the support for the missing 9735,9855,9755 and 9715 chips. And another remark: The 9735 and 9835 seem to be chips with serial *and* parallel interfaces, so I suppose they are already claimed somewhere in the serial driver. I don't know whether this causes any problems. I'm sorry that I can't test, I've only a 9805 here. Any idea how these "dual" chips have to be handled by the kernel? Signed-off-by:
-
Torben Mathiasen authored
Patch brings devices.txt up-to-date with LANANA. Signed-off-by:
-
Torben Mathiasen authored
I took over LANANA maintainership from John Cagle. Patch updates MAINTAINERS accordingly. Signed-off-by:
-
Andrew Morton authored
As David M-T points out, the default per-user mlock limit should be at least a single page. Signed-off-by:
-
William Lee Irwin III authored
Unaccount VM_DONTCOPY vmas properly; the child inherits the whole of the parent's virtual accounting from the memcpy() in copy_mm(), but the VM_DONTCOPY check here is where a decision is made for the child not to inherit the vmas corresponding to some accounted memory usages. Hence, unaccount them when skipping over them here. Signed-off-by:
-
William Lee Irwin III authored
Account reserved memory properly as per acahalan's speecified semantics. Signed-off-by:
-
William Lee Irwin III authored
Remove the accounting overhead when CONFIG_PROC_FS is not defined. Signed-off-by:
-
William Lee Irwin III authored
Some kind of brainfart happened here, though it's not visible on the default display from top(1) etc. This patch fixes up the gibberish I mistakenly put down for text with the proper text size, and subtracts it from data as per the O(vmas) code beforehand. Signed-off-by:
-
William Lee Irwin III authored
Merely removing down_read(&mm->mmap_sem) from task_vsize() is too half-assed to let stand. The following patch removes the vma iteration as well as the down_read(&mm->mmap_sem) from both task_mem() and task_statm() and callers for the CONFIG_MMU=y case in favor of accounting the various stats reported at the times of vma creation, destruction, and modification. Unlike the 2.4.x patches of the same name, this has no per-pte-modification overhead whatsoever. This patch quashes end user complaints of top(1) being slow as well as kernel hacker complaints of per-pte accounting overhead simultaneously. Signed-off-by:
-
William Lee Irwin III authored
task_vsize() doesn't need mm->mmap_sem for the CONFIG_MMU case; the semaphore doesn't prevent mm->total_vm from going stale or getting inconsistent with other numbers regardless. Also, KSTK_EIP() and KSTK_ESP() don't want or need protection from mm->mmap_sem either. So this pushes mm->mmap_sem to task_vsize() in the CONFIG_MMU=n task_vsize(). Also, hoist the prototype of task_vsize() into proc_fs.h The net result of this is a small speedup of procps for CONFIG_MMU. Signed-off-by:
-
Dave Hansen authored
asm/page.h seems to be the accepted place to declare virt_to_page() on a vast majority of architectures. This patch makes sure that a few files which use that function also directly include the header. Signed-off-by:
Dave Hansen <haveblue@us.ibm.com> Signed-off-by:
-
Dave Hansen authored
__pa() is always be consistent inside of a single page. The next thing virt_to_page() does after that is shift down the address, killing the bits that __change_page_attr() just masked off. Remove the superfluous masking. Signed-off-by:
-
Dave Hansen authored
Store the physical pgd address in a different variable than the virtual address. There's no real reason to only use 1 variable here, other than saving a line of code. But, the types really are different and we might as well just spell that out explicitly. Signed-off-by:
-
Dave Hansen authored
I'm sure there's a good reason for these functions to take virtual addresses as unsigned longs, so suppress the warnings and cast them to the proper types before calling the virt/phys conversion functions A perfectly acceptable alternative would be to go and change free_pages() to stop taking unsigned longs for virtual addresses, but this has a much smaller impact. Signed-off-by:
-
Dave Hansen authored
__pa() should take a void*. This adds the proper cast. Signed-off-by:
-
Dave Hansen authored
Ran across this because it's another place where an unsigned long is passed directly to __pa(). Making the "page" variable a void* seems a bit more natural than an unsigned long and reduces the net number of casts by 1. Without it, we probably need another (void *) cast in the __pa() call. For more explanation as to why this was probably done originally, see this post: http://marc.theaimsgroup.com/?l=linux-mm&m=109155379124628&w=2Signed-off-by:
-
Pierre Ossman authored
The kernel currently allocates the range 0x40-0x5f for timer calls. This causes conflicts with other hardware using these ports (In my case a Winbond W83L519D SD/MMC card reader). This patch splits the resource into the ports actually needed. Signed-off-by:
-
John Levon authored
Anton prompted me to get this patch merged. It changes the core buffer sync algorithm of OProfile to avoid global locks wherever possible. Anton tested an earlier version of this patch with some success. I've lightly tested this applied against 2.6.8.1-mm3 on my two-way machine. The changes also have the happy side-effect of losing less samples after munmap operations, and removing the blind spot of tasks exiting inside the kernel. Signed-off-by:
-
Andrew Morton authored
davem says that copy_mount_options is failing in obscure ways if the architecture's copy_from_user() doesn't return an exact count of the number of uncopied bytes. Fixing that up in each architecture is a pain - it involves falling back to byte-at-a-time copies. It's simple to open-code this in namespace.c. If we find other places in the kernel which care about this we can promote this to a global function. Signed-off-by:
-
Roland McGrath authored
When the initial thread in a multi-threaded program dies (the thread group leader), its child processes are wrongly orphaned, and thereafter when other threads die their child processes are also orphaned even though live threads remain in the parent process that can call wait. I have a small (under 100 lines), POSIX-compliant test program that demonstrates this using -lpthread (NPTL) if anyone is interested in seeing it. The bug is that forget_original_parent moves children to the dead parent's group leader if it's alive, but if not it orphans them. I've changed it so it instead reparents children to any other live thread in the dead parent's group (not even preferring the group leader). Children go to init only if there are no live threads in the parent's group at all. These are the correct semantics for fork children of POSIX threads. The second part of the change is to do the CLONE_PARENT behavior always for CLONE_THREAD, i.e. make sure that each new thread's parent link points to the real parent of the process and never another thread in its own group. Without this, when the group leader dies leaving a sole live thread in the group, forget_original_parent will try to reparent that thread to itself because it's a child of the dying group leader. Rather handling this case specially to reparent to the group leader's parent instead, it's more efficient just to make sure that noone ever has a parent link to inside his own thread group. Now the reparenting work never needs to be done for threads created in the same group when their creator thread dies. The only change from losing the who-created-whom information is when you look at "PPid:" in /proc/PID/task/TID/status. For purposes of all direct system calls, it was already as if CLONE_THREAD threads had the parent of the group leader. (POSIX provides no way to keep track of which thread created which other thread with pthread_create.) Signed-off-by:
Roland McGrath <roland@redhat.com> Signed-off-by:
-
Rusty Russell authored
MODULE_PARM() was marked obsolete. Remove it from everything except drivers/ and arch/. Naturally, such a widespread change may introduce bugs for some of the non-trivial cases, and where in doubt I used "0" as permissions arg (ie. won't appear in sysfs). Individual authors should think about whether that would be useful. Signed-off-by:
Rusty Russell <rusty@rustcorp.com.au> Signed-off-by:
-
Jeff Mahoney authored
I saw a recent bug report that showed when a process set up a dnotify against the autofs root and then attempted an access(2) call inside the autofs namespace on a mount that would fail, it would create a signal/restart loop. The cause is that the autofs code checks to see if any signals are pending after it waits on a response from the autofs daemon. If it finds any, it assumes that autofs_wait was interrupted, and that it should return -ERESTARTNOINTR. The problem with this is that a signal_pending(current) check will return true if *any* signals were received, not just if a signal that interrupted the wait was received. autofs_wait explicitly blocks all signals except for SIGKILL, SIGQUIT, and SIGINT before calling interruptible_sleep_on. The effect is that if a dnotify is set against the autofs root, when the autofs daemon creates the directory, a dnotify event will be sent to the originating process. Since the code in autofs_root_lookup doesn't check to see what signals are actually pending, it bails early, telling the caller to try again. The loop goes on forever until interrupted via one of the actual interrupting signals. The following patch makes both autofs_root_lookup and autofs4_root_lookup verify that one of its defined "shutdown" signals are pending before bailing out early. Any other signal should be delivered later, as expected. It doesn't matter if the signal occured outside of the sleep in autofs_wait. The calling process will either go away or try again. Signed-off-by:
-
