- 20 Oct, 2004 40 commits
-
-
Phil Oester authored
The scsihosts boot parameter was removed in 2.5.73, but references to it still exist in docs. Cleanup below. Signed-off-by:
Andrew Morton <akpm@osdl.org> Signed-off-by:
Linus Torvalds <torvalds@osdl.org>
-
Stephen C. Tweedie authored
The orphan list holds inodes that need to be truncated on recovery. In the O_DIRECT case, it's used if we extend the inode --- the truncate on recovery means we'll recover the newly-allocated disk blocks if we crash after the IO starts but before i_size is updated on disk. Now, the orphan list is *also* used to delete inodes that are unlinked but still-open. Those get truncated but also deleted on recovery. The orphan list is held both in memory and on disk. So the rules are that the inode can't be reclaimed while on the orphan list. There are only two cases --- either the inode is actively being written(O_DIRECT) or truncated (in which case the inode is by definition not going to be reused), or it's unlinked but still open (again, non-reclaimable). But in the case where you're truncating or write(O_DIRECT)ing a file that is *ALSO* unlinked, there's a problem --- the final unlink would put the inode on the orphan list, but the write/truncate would try to add/remove it. End result is that the inode disappears from the orphan list while it's still unlinked-but-in-use. That's just a leak-on-crash, it's not going to be detectable in normal use. But it's still a bug, and the way we fix it is for direct-IO and truncate not to do the ext3_orphan_del if the file is unlinked (ie. i_nlink==0). Signed-off-by:
-
William A. Adamson authored
Add the new lock manager callbacks to the documentation Signed-off-by:
Andy Adamson <andros@citi.umich.edu> Signed-off-by:
-
William A. Adamson authored
Export remove_lease(), an interface to time_out_leases() with an fl_break_time in the past. needed by nfsd Signed-off-by:
-
William A. Adamson authored
Export setlease(), a direct interface to __setlease() used by nfsd Signed-off-by:
-
William A. Adamson authored
Use the inode i_writecount to test for handing out a F_RDLCK lease. Signed-off-by:
-
William A. Adamson authored
nfsd will not have a file descriptor, nor an owner on the filp. nfsd also will not use signals. Seperate the lease processsing coe from fcntl_setlease() into a __setlease() call. Signed-off-by:
-
William A. Adamson authored
Move the f_delown processing from lease_modify() into a new default lock manager fl_release_private callback. Signed-off-by:
-
William A. Adamson authored
Separate the lease initialization code from lease_alloc(). set the default lock manager ops. Signed-off-by:
-
William A. Adamson authored
- Add a lock manager break callback to break_lease() for lock managers to initiate breaking a lease. - Move the break_lease() kill_fasync() call to a default lock manager fl_break callback Signed-off-by:
-
William A. Adamson authored
Add a lock manager release private callback to locks_free_lock() for lock manger lease clean-up. Signed-off-by:
-
William A. Adamson authored
The following patches provide an interface to the lease subsystem in the current VFS locking code. NFSv4 delegations and Samba op-locks share most architecture features. The version 4 NFS server delegation implementation should use leases to co-ordinate behavior between local, Samba, and NFS access. The main design points are - Seperate the fcntl interface from the file_lock FL_LEASE processing in fcntl_setlease, creating __setlease() called by fcntl_setlease() - Add new lock_manager callbacks to enable lease properties to be set, leases to be broken, and leases to be cleaned up: with default callbacks preserving the current fcntl_setlease properties. - Add a new interface, setlease() which also calls __setlease(), and remove_lease() for kernel lease managers (e.g. the v4 NFS server) This patch: Add a lock manager copy lock callback to locks_copy_lock() so that nfsd can set lease properties. Signed-off-by:
-
Jeff Mahoney authored
This patch uses the REISERFS_UNSUPPORTED_OPT flag to denote -o(no)acl, and -o(no)user_xattr as unsupported, but allowable, when support isn't built into the kernel. Signed-off-by:
Jeff Mahoney <jeffm@novell.com> Signed-off-by:
-
Jeff Mahoney authored
This patch adds a REISERFS_UNSUPPORTED_OPT flag to denote when a mount option is allowable, but is unsupported in the running configuration. This allows the potential for the set of mount options to be consistent, regardless of what features the kernel is compiled with. Rather than failing the mount, a warning is issued and the mount succeeds. Signed-off-by:
-
Kenneth W. Chen authored
Config option CONFIG_SCHEDSTATS is currently enabled via arch specific Kconfig.debug. Only x86 and ppc arches has code to turn it on. Why not put it in generic lib/Kconfig.debug so it is done once to enable everyone? Signed-off-by:
Ken Chen <kenneth.w.chen@intel.com> Signed-off-by:
-
Armin Schindler authored
The file Documentation/isdn/README.eicon is outdated and obsolete in kernel 2.6. This file includes description of the old Eicon ISDN driver in kernel 2.4, which was removed in 2.6. Signed-off-by:
-
Adrian Bunk authored
Signed-off-by:
Chris Wright <chrisw@osdl.org> Signed-off-by:
Adrian Bunk <bunk@stusta.de> Signed-off-by:
-
Adrian Bunk authored
kernel/built-in.o(.text+0x1d42b): In function `crash_create_proc_entry': : undefined reference to `proc_vmcore' Signed-off-by:
-
Keith Owens authored
Treat .pci_fixup entries the same as .init code/data. Signed-off-by:
Keith Owens <kaos@ocs.com.au> Signed-off-by:
-
Dean Gaudet authored
This patch adds efficeon as a cpu option, and makes a small update to the transmeta cpuid code. (i wasn't sure if the various doc files are UTF-8... if they are, then the e should be a U-275 ;) The compile options may not be ideal, but they're probably close. i used -march=pentium3, but -march=pentium4 would have been good enough too. The cpuid update teaches transmeta.c about the extended processor revision present in cpuid level 0x80860002... the external documentation does not indicate how to break apart this field, and instructs only that the 32-bit value should be printed in hex (alas). Signed-off-by:
dean gaudet <dean@arctic.org> Signed-off-by:
-
Maciej W. Rozycki authored
I've noticed that under specific circumstances the "console=" kernel parameter is ignored. This happens when EARLY_PRINTK is enabled and the serial console is the only available. In this case unregister_console() when called for the early console sets preferred_console back to -1 replacing the value that was recorded by console_setup() -- the order of calls is as follows: 1. register_console() -- for the early console, 2. console_setup() -- recording the console index for the real console, 3. unregister_console() -- for the early console, erasing the console index recorded above, 4. register_console() -- for the real console, picking up the first device available, instead of the selected one. I've observed this problem with a DECstation system using ttyS3 -- its default console device from the firmware's point of view. The solution is to restore the setting of "console=" upon unregister_console(). This made a snapshot of 2.4.26 work for me. I wasn't able to test the changes with 2.6 because DECstation drivers don't support it yet, but the code responsible for console selection appears functionally the same. So I've concluded it needs the same change. Here's a patch. Signed-off-by:
-
Matthieu Castet authored
Signed-off-by:
-
Ed Schouten authored
At the moment, the NLM cookie length is fixed to 8 bytes, while 1024 is the theoretical maximum. FreeBSD uses 16 bytes, Mac OS X uses 20 bytes. Therefore we need to make the length dynamic (which I set to 32 bytes). This patch is based on an old patch for Linux 2.4.23-pre9, which I changed to patch properly (also added some stylish NIPQUAD fixes). From: Neil Brown <neilb@cse.unsw.edu.au> Further lockd tidyups. - NIPQUAD everywhere that is appropriate - use XDR_QUADLEN in more places as appropriate - discard QUADLEN which is a lockd-specific version of XDR_QUADLEN Signed-off-by:
Neil Brown <neilb@cse.unsw.edu.au> Signed-off-by:
-
Neil Brown authored
While %Lu works with gcc, %llu is the correct usage. Signed-off-by:
-
Manfred Spraul authored
Attached is a patch that fixes the fragmentation that Badri noticed with kmem_cache_alloc_node. kmem_cache_alloc_node tries to allocate memory from a given node. The current implementation contains two bugs: - the node aware code was used even for !CONFIG_NUMA systems. Fix: inline function that redefines kmem_cache_alloc_node as kmem_cache_alloc for !CONFIG_NUMA. - the code always allocated a new slab for each new allocation. This caused severe fragmentation. Fix: walk the slabp lists and search for a matching page instead of allocating a new page. - the patch also adds a new statistics field for node-local allocs. They should be rare - the codepath is quite slow, especially compared to the normal kmem_cache_alloc. Signed-Off-By:
Manfred Spraul <manfred@colorfullife.com> Signed-off-by:
-
Marcelo Tosatti authored
There is a useless AND in swp_type() function. We just shifted right SWP_TYPE_SHIFT() bits the value from the swp_entry_t, and then we AND it with "(1 << 5) - 1" (which is a mask corresponding to the number of bits used by "type"). Signed-off-by:
-
Dinakar Guniguntala authored
/proc shows the wrong PID as parent in the following case Process A creates Threads 1 & 2 (using pthread_create) Thread 2 then forks and execs process B getppid() for Process B shows Process A (rightly) as parent, however /proc/B/status shows Thread 3 as PPid (incorrect). Signed-off-by:
Dinakar Guniguntala <dino@in.ibm.com> Acked-by:
Ingo Molnar <mingo@elte.hu> Signed-off-by:
-
Adrian Bunk authored
There's no reason to directly #include <asm/bitops.h> since it's available on all architectures and also included by #include <linux/bitops.h>. This patch changes #include <asm/bitops.h> to #include <linux/bitops.h>. Signed-off-by:
-
Dave Hansen authored
I don't know what this is trying to do. It might be some kind of artifact from when get_pgd_slow() was removed. The expanded expression with __pa() ends up looking something like this: (unsigned long)(u64)(u32)pmd-PAGE_OFFSET and that is just nutty because pmd is a pointer now, anyway. Attached patch removes the casts. Signed-off-by:
Dave Hansen <haveblue@us.ibm.com> Signed-off-by:
-
Paolo \'Blaisorblade\' Giarrusso authored
Use, in the rb_entry definition, the container_of macro instead of reinventing the wheel; compared to using offset_of() as I did in the prev. version, it has type safety checking. Signed-off-by:
Paolo 'Blaisorblade' Giarrusso <blaisorblade_spam@yahoo.it> Signed-off-by:
-
Pavel Machek authored
Overwrite __init section so calls to __init functions from normal code are caught, reliably. (Plus a fix from Dave Hansen) Signed-off-by:
-
Andrew Morton authored
remove unneeded preempt_disable/enable. pte_offset_map/unmap already does that. Signed-off-by:
-
Jesper Juhl authored
Signed-off-by:
Jesper Juhl <juhl-lkml@dif.dk> Signed-off-by:
-
Matt Domsch authored
Separate the module source and header checksum into a separate modinfo field srcversion. With CONFIG_MODULE_SRCVERSION_ALL=y, put srcversion into every module, not just those with MODULE_VERSION("something"). Patch by Rusty Russell, trivial merging and testing by Matt Domsch Signed-off-by:Matt Domsch <Matt_Domsch@dell.com> Signed-off-by:
Rusty Russell <rusty@rustcorp.com.au> Signed-off-by:
-
Matt Domsch authored
Below is a patch to suppress printing uninformative errors from ide-floppy.c in response to commands to floppy drives in which no media is present. Without this patch, commands sent to ide-floppy devices without media inserted cause error messages on the console (KERN_ERR level) such as: ide-floppy: ide: I/O error, pc = 0 key = 2, asc = 3a asq = 0 ide-floppy: ide: I/O error, pc = 1b key = 2, asc = 3a asq = 0 ide-floppy: ide: I/O error, pc = 23 key = 2, asc = 3a asq = 0 ide-floppy: ide: I/O error, pc = 1e key = 2, asc = 3a asq = 0 ide-floppy: ide: I/O error, pc = 1e key = 2, asc = 3a asq = 0 Dell's Virtual Floppy (system management presents to the local system an IDE floppy device, which is actually a floppy device in a remote system connected over an IP link) exhibits this also, when connecting to a remote floppy drive with no media present. Signed-off-by:
-
Colin Leroy authored
This one fixes another unitialized var warning (which is harmless, but whatever). Signed-off-by:
Colin Leroy <colin@colino.net> Signed-off-by:
-
Hideo Aoki authored
In Documentation/filesystems/proc.txt, explanation of /proc/meminfo is described in section 1.3 (IDE devices in /proc/ide). I think that it should be described in section 1.2 (Kernel data). Signed-off-by:
Hideo Aoki <aoki@sdl.hitachi.co.jp> Signed-off-by:
-
Hideo Aoki authored
This patch adds "swap_token_timeout" parameter in /proc/sys/vm. The parameter means expired time of token. Unit of the value is HZ, and the default value is the same as current SWAP_TOKEN_TIMEOUT (i.e. HZ * 300). Signed-off-by:
-
Matt Domsch authored
Some controller BIOSes have problems with the legacy int13 fn02 READ SECTORS command. int13 fn42 EXTENDED READ is used in preference by most boot loaders today, so lets use that. If EXTENDED READ fails or isn't supported, fall back to READ SECTORS. This hopefully resolves the three reports of BIOSes which would either long-pause (30+ seconds) or hang completely on the legacy READ SECTORS command. This also adds CONFIG_EDD_SKIP_MBR to eliminate reading the MBR on each BIOS-presented disk, in case there are further problems in this area. Signed-off-by:
-
Ryan S. Arnold authored
This patch prevents execution of hvc_write() and hvc_hangup() after the tty layer has executed a final hvc_close() against a device. This patch provides a better method than was previously used. tty->driver_data is no longer invalidated so we'll no longer get oopses when the tty layer allows late hangup() and write() operations. - Removed silly tty->driver_data = NULL; from hvc_close which prevents possible oops in hvc_write() and hvc_hangup() due to improperly acting ldisc close ordering. - Added hp->count <= 0 check to hvc_write() and hvc_hangup() to prevent execution of these function after hvc_close() has been invoked by the tty layer. Same tty ldisc issues as above are the reason. - Added some comments to clarify the situation. - Awaiting a forth coming patch from Alan Cox which should clean up the close ordering and prevent the late hangup and write ops from happening. Signed-off-by:
Ryan S. Arnold <rsa@us.ibm.com> Signed-off-by:
-
