- 08 Sep, 2004 40 commits
-
-
Dave Jones authored
Not that this driver compiles, but coverity picked up this nonsense. If the pci_alloc_consistent fails, we go boom. Amusingly, after the ==NULL check, is an identical memset. Signed-off-by:
Dave Jones <davej@redhat.com> Signed-off-by:
Andrew Morton <akpm@osdl.org> Signed-off-by:
Linus Torvalds <torvalds@osdl.org>
-
Antonino Daplas authored
This adds module_init(xxxfb_init) in all drivers. For drivers with xxxfb_setup(), this patch also adds a 'xxxfb_setup(fb_get_options("xxxfb"))' prior to initialization. Signed-off-by:Antonino Daplas <adaplas@pol.net> Signed-off-by:
Adrian Bunk <bunk@fs.tum.de> Signed-off-by:
-
Antonino Daplas authored
This patch probably deserves discussion among developers. Currently, the framebuffer system is initialized in a roundabout manner. First, drivers/char/mem.c calls fbmem_init(). fbmem_init() will then iterate over an array of individual drivers' xxxfb_init(), then each driver registers its presence back to fbmem. During console_init(), drivers/char/vt.c will call fb_console_init(). fbcon will check for registered drivers, and if any are present, will call take_over_console() in drivers/char/vt.c. This patch changes the initialization sequence so it proceeds in this manner: Each driver has its own module_init(). Each driver calls register_framebuffer() in fbmem.c. fbmem.c will then notify fbcon of the driver registration. Upon notification, fbcon calls take_over_console() in vt.c. The following are the changes brought about by this patch: - Each subsystem (fbcon, fbmem, xxxfb) will have their own module_init. Thus, explicit calls to each subsystem's init functions are eliminated. - The struct fb_drivers array in fbmem.c can be removed. This slashes around 400 lines in fbmem.c - Parsing of kernel boot options were done by fbmem.c calling each driver's xxxfb_setup() function. Because this is not possible with this patch, drivers can choose to either: - have their own __setup() routine - call fb_get_options("xxxfb") and pass the return value to xxxfb_setup(). This is to maintain compatibility with the 'video=xxxfb:<options>' semantics. - Getting a framebuffer console will occur a bit late during the boot process since the initialization sequence will depend upon the link order. So, 'video/' is moved up in drivers/Makefile, shortly after 'pci/' - Because driver initialization will be dependent on the link order, hardware that depends on other subsystems (agpgart, usb, serial, etc) may choose to initialize after the subsystems they depend on. Signed-off-by: -
Antonino Daplas authored
- This fixes another regression from 2.4. If fbcon is compiled statically, and the framebuffer driver is compiled as a module, doing a 'modprobe xxxfb' does nothing to the console. This has generated numerous bug reports from users. With this patch, fbmem will notify fbcon upon driver registration allowing fbcon to take over the console. - This also fixes con2fbmap not working if fbcon is compiled as a module using the same mechanism as described above. Signed-off-by:
-
Antonino Daplas authored
- Fixed rivafb crashing in PPC. rivafb in PPC requires full, instead of partial, hardware initialization in rivafb_set_par(). - Added untested support for NV_ARCH_30 chipsets. - From Guido Guenther <agx@sigxcpu.org> here's another short patch fixing the cursor colors on big endian. - From Guido Guenther <agx@sigxcpu.org> trivial: strictmode is a MODULE_PARAM, even if CONFIG_MTRR is not set: Signed-off-by:Guido Guenther <agx@sigxcpu.org> Signed-off-by:
-
Antonino Daplas authored
This patch speeds up scrolling of tdfxfb by maximizing var->yres_virtual so tdfxfb uses SCROLL_PAN_MOVE instead of SCROLL_REDRAW. This is true whether CONFIG_FB_3DFX_ACCEL is set or not. This problem was reported by Paolo Ornati <ornati@fastwebnet.it> who also made substantial contributions to solve this problem. This patch also fixes compile errors when CONFIG_FB_3DFX_ACCEL is false. Signed-off-by:
-
Dave Jones authored
This looks awry. Move the dereference to after we have checked sb is non-NULL. Signed-off-by:
-
Tom Rini authored
The following patch switches arch/ppc/boot over from using its own version of zlib to the code found under lib/zlib_inflate. In conjunction with the previous two patches, the size of the resulting images isn't noticably different. But this does have the advantage of removing another copy of zlib from the kernel, and I believe this allows for lib/inflate.c to go away (as that's basically what ppc used to use). Signed-off-by:
Tom Rini <trini@kernel.crashing.org> Signed-off-by:
-
Tom Rini authored
The following changes zlib_inflate_trees_fixed(...) from using a statically defined table, to generating this table. This cuts out 4-8kB from inftrees.o (4kB on IBM 440GP, 8kB on PPC 74xx). Signed-off-by:
-
Tom Rini authored
The following patch moves zlib_inflateSync and friends, which are used by PPP and not a 'normal' gzip, into inflate_sync.c. Signed-off-by:
-
Martin Schwidefsky authored
From: Thomas Spatzier <tspat@de.ibm.com> lcs network driver changes: - Fix deadlock on card->ipm_lock. Signed-off-by:
Martin Schwidefsky <schwidefsky@de.ibm.com> Signed-off-by:
-
Martin Schwidefsky authored
The different stack frame layout for packed stacks broke cpu hotplug. Recreate the initial stack frame of the idle thread for offline cpus coming back online. Reenable interrupts after loading the initial registers. In addition this patch contains two more bug fixes: a typo for 64 bit (__SMALL_STACK_SIZE vs. __SMALL_STACK) and show_trace didn't show a trace if for task == NULL. Signed-off-by:
-
Martin Schwidefsky authored
Removes unnecessary min/max macros and changes calls to use kernel.h macros instead. Signed-off-by:
Michael Veeck <michael.veeck@gmx.net> Signed-off-by:
Maximilian Attems <janitor@sternwelten.at> Signed-off-by:
-
Bastian Blank authored
The attached patch exports __copy_in_user_asm for s390. It is used in xfs. Signed-off-by:
-
Andrew Morton authored
It has no callers. Signed-off-by:
-
Brian Gerst authored
This patch removes the default stubs for init_module and cleanup_module, and checks for NULL instead. It changes modpost to only create references to those functions if they actually exist. Signed-off-by:
-
Neil Brown authored
No need to set fl_owner and fl_pid to 0, since that's already been done by locks_init_lock. Signed-off-by:
Andy Adamson <andros@umich.edu> Signed-off-by:
J. Bruce Fields <bfields@citi.umich.edu> Signed-off-by:
Neil Brown <neilb@cse.unsw.edu.au> Signed-off-by:
-
Neil Brown authored
The file_lock.fl_pid is no longer used in posix_same_owner() tests. So just set it to current->tgid for informational purposes. Signed-off-by:
-
Neil Brown authored
Postpone the release of a stateowner on CLOSE for lease time to enable the CLOSE replay cache. Place stateowner on the close_lru list to be reaped by the laundromat service. Signed-off-by:
-
Neil Brown authored
nfsd4 could leak a stateid in a case of kmalloc failure; fix. Signed-off-by:
-
Neil Brown authored
Whitespace cleanup, fix one dprintk, remove superfluous casts of NULL. Signed-off-by:
-
Neil Brown authored
The nfs4 attributes supported_attrs and aclsupport should not be static; they need to depend on the exported filesystem's acl support. Test the latter by attempting to get an acl, and adjust the returned attributes apropriately. Signed-off-by:
-
Neil Brown authored
fix incorrect indentation in fh_verify Signed-off-by:
-
Neil Brown authored
As 'nfs_acceptable' uses the authnetication user in it's checks, the filehandle might not be truely "stale" - EACCES is safer. Thanks Olaf Kirch <okir@suse.de> and others. Signed-off-by:
-
Neil Brown authored
If we would block, we return "err-jukebox" for nfsv3, or just drop the request for v2. Signed-off-by:
-
Neil Brown authored
This error only affects two message (and sysadmin heart-rate). It does not risk data. Signed-off-by:
-
Marcelo Tosatti authored
filemap_fdatawait() calls wait_on_page_writeback_range() with -1 as "end" parameter. This is not needed since we know the EOF from the inode. Use that instead. Signed-off-by:
Marcelo Tosatti <marcelo.tosatti@cyclades.com> Signed-off-by:
-
Roland Dreier authored
Currently the BKL is used to synchronize access to ioctl32_hash_table in fs/compat.c. It seems that an rwsem would be more appropriate, since this would allow multiple lookups to occur in parallel (and also serve the general good of minimizing use of the BKL). I added lock_kernel()/unlock_kernel() around the call to t->handler when a compatibility handler is found in compat_sys_ioctl() to preserve the expectation that the BKL will be held during driver ioctl operations. It should be safe to do lock_kernel() while holding ioctl32_sem because of the magic BKL sleep semantics. Signed-off-by:
Roland Dreier <roland@topspin.com> Signed-off-by:
-
Christoph Hellwig authored
These are only used by the out of tree linux-abi project, so it makes sense to define them in those modules. Signed-off-by:
-
Christoph Hellwig authored
This patch adds common nls_tolower, nls_toupper and nls_strnicmp helpers to nls.h and uses them in various filesystems instead of local duplicates. The situation for ncpfs isn't as nice as it allows to compile without nls support even if the kernel has CONFIG_NLS set, so we need wrappers there. Signed-off-by:
-
Manfred Spraul authored
The kernel contains an optimization that skips the linked list walk in get_tgid_list for the common case of sequential accesses. Unfortunately the optimization is buggy (missing NULL pointer check for the result of find_task_by_pid) and broken (actually - broken twice: the tgid value that is stored in f_version is always 0 because tgid is overwritten when the string is created and additionally the common case is not filldir < 0, it's running out of nr_tgids). The attached patch fixes these bugs. Roger Luethi <rl@hellgate.ch> ran a benchmark: test: top -d 0 -b -n 10 > /dev/null ==> 2.6.8 <== real 0m19.092s user 0m5.013s sys 0m12.622s ==> 2.6.8 + patch-tgid-bugfixes <== real 0m10.062s user 0m5.042s sys 0m4.111s Signed-Off-By:
Manfred Spraul <manfred@colorfullife.com> Signed-off-by:
-
Ram Pai authored
Fix the do_generic_file_read()-reads-one-page-too-many-bug for the fifth time. This patch combines the best features from Nick's patch and also makes index and end_index consistent. (i.e index 'n' covers n*PAGE_SIZE to ((n+1)PAGE_SIZE)-1. I did not feel comfortable with the way index and end_index represented different ranges. It was like comparing apples with oranges. Signed-off-by:
-
Ken Preslan authored
Below is a patch that lets a cluster filesystem (such as GFS) implement flock across the cluster. Signed-off-by:
-
Andy Polyakov authored
Fix a few range checks which aren't working right because if (int < sizeof(...)) does the wrong thing if `int' is negative, due to `sizeof' returning unsigned. In addition to comparisons, the patch makes CDROMVOL* ioctl more robust. Signed-off-by:
-
Roland McGrath authored
On x86 and x86-64, setting up to run a signal handler clears the single-step bit (TF) in the processor flags before starting the handler. This makes sense when a process is handling its own SIGTRAPs. But when TF is set because PTRACE_SINGLESTEP was used, and that call specified a handled signal so the handler setup is happening, it doesn't make so much sense. When the debugger stops to show you a signal about to be delivered, and that signal should be handled, and then you do step or stepi, you expect to see the signal handler code. In fact, the signal handler runs to completion and then you see the single-step trap at the resumed code instead of seeing the handler. This patch changes signal handler setup so that when TF is set and the thread is under ptrace control, it synthesizes a single-step trap after setting up the PC and registers to start the handler. This makes that PTRACE_SINGLESTEP not strictly a "step", since it actually runs no user instructions at all. But it is definitely what a debugger user wants, so that single-stepping always stops and shows each and every instruction before it gets executed. Signed-off-by:
Roland McGrath <roland@redhat.com> Signed-off-by:
-
Roland McGrath authored
In 2.4, strace will show you all bogus system calls a process tries. In 2.6, it only shows you stubs < __NR_syscalls, and there is no tracing stop for large bogus system call numbers. I can't see why this was changed, so I am assuming it was accidental. This patch restores the expected behavior that syscall tracing shows every bogus syscall attempt. Signed-off-by:
-
Roland McGrath authored
After my cleanup of the rusage semantics was so quickly taken in by Andrew and Linus without comment, I wonder if I should not have tried to be so accommodating of potential objections as I was. :-) In my original posting, I solicited comment on whether introducing RUSAGE_GROUP as distinct from RUSAGE_SELF was warranted. Note that we've now changed the behavior of the times system call when using CLONE_THREAD, so changing getrusage RUSAGE_SELF to match would be consistent. I think that changing the meaning of the old RUSAGE_SELF value is preferable to introducing the new value for the proper POSIX getrusage behavior. This patch against Linus's current tree dumps RUSAGE_GROUP and makes RUSAGE_SELF have the fixed behavior. If there is interest in having a new explicit interface to sample a single thread's stats alone, then I think that would be better done by introducing a new value for RUSAGE_THREAD. This is trivial to implement, but I won't offer patches bloating the interface if noone is actually interested in using it. Signed-off-by:
-
Roland McGrath authored
This makes any ptrace operation that finds the target in TASK_STOPPED state morph it into TASK_TRACED state before doing anything. This necessitates reverting the last_siginfo accesses to check instead of assume last_siginfo is set, since it's no longer impossible to be in TASK_TRACED without being stopped in ptrace_stop (though there are no associated races to worry about). Signed-off-by:
-
Roland McGrath authored
This adds a new state TASK_TRACED that is used in place of TASK_STOPPED when a thread stops because it is ptraced. Now ptrace operations are only permitted when the target is in TASK_TRACED state, not in TASK_STOPPED. This means that if a process is stopped normally by a job control signal and then you PTRACE_ATTACH to it, you will have to send it a SIGCONT before you can do any ptrace operations on it. (The SIGCONT will be reported to ptrace and then you can discard it instead of passing it through when you call PTRACE_CONT et al.) If a traced child gets orphaned while in TASK_TRACED state, it morphs into TASK_STOPPED state. This makes it again possible to resume or destroy the process with SIGCONT or SIGKILL. All non-signal tracing stops should now be done via ptrace_notify. I've updated the syscall tracing code in several architectures to do this instead of replicating the work by hand. I also fixed several that were unnecessarily repeating some of the checks in ptrace_check_attach. Calling ptrace_check_attach alone is sufficient, and the old checks repeated before are now incorrect, not just superfluous. I've closed a race in ptrace_check_attach. With this, we should have a robust guarantee that when ptrace starts operating, the task will be in TASK_TRACED state and won't come out of it. This is because the only way to resume from TASK_TRACED is via ptrace operations, and only the one parent thread attached as the tracer can do those. This patch also cleans up the do_notify_parent and do_notify_parent_cldstop code so that the dead and stopped cases are completely disjoint. The notify_parent function is gone. Signed-off-by:
-
Christoph Hellwig authored
Since the irq handling rework in 2.5 lots of code in the individual <asm/hardirq.h> files is the same. This patch moves that common code to <linux/hardirq.h>. The following differences existed: - alpha, m68k, m68knommu and v850 were missing the ~PREEMPT_ACTIVE masking in the CONFIG_PREEMPT case of in_atomic(). These architectures don't support CONFIG_PREEMPT else this would have been an easily-spottbale bug - S390 didn't provide synchronize_irq as it doesn't fit into their I/O model. They now get a spurious prototype/macro - ppc added a new preemptible() macro that is provided for all architectures now. Most drivers were using <linux/interrupt.h> as they should, but a few drivers and lots of architecture code has been updated to use <linux/hardirq.h> instead of <asm/hardirq.h> Signed-off-by:
-
