- 17 Apr, 2004 15 commits
-
-
Andrew Morton authored
From: NeilBrown <neilb@cse.unsw.edu.au> From: "J. Bruce Fields" <bfields@fieldses.org> From: Andros: Hold state_lock longer so the stateowner doesn't diseappear out from under us before we get the chance to encode the replay. Don't attempt to save replay if we failed to find a stateowner.
-
Andrew Morton authored
From: NeilBrown <neilb@cse.unsw.edu.au> From: "J. Bruce Fields" <bfields@fieldses.org> From: Andros: locku replies should be saved for possible replay as well.
-
Andrew Morton authored
From: NeilBrown <neilb@cse.unsw.edu.au> From: "J. Bruce Fields" <bfields@fieldses.org> From: Andros: Idea is to keep around a list of openowners recently released by closes, and make sure they stay around long enough so that replays still work.
-
Andrew Morton authored
From: NeilBrown <neilb@cse.unsw.edu.au> From: "J. Bruce Fields" <bfields@fieldses.org> Error return when the client supplies a bad service should be badcred.
-
Andrew Morton authored
From: NeilBrown <neilb@cse.unsw.edu.au> From: "J. Bruce Fields" <bfields@fieldses.org> Fix out-of-spec errors in nfs4 readdir. Add checks for bad cookie values. (plus compile fix from akpm)
-
Andrew Morton authored
From: Kevin Corry <kevcorry@us.ibm.com> Striped: Use an EMIT macro in the status function.
-
Andrew Morton authored
From: Kevin Corry <kevcorry@us.ibm.com> dm-ioctl.c::retrieve_status(): Prevent overrunning the ioctl buffer by making sure we don't call the target status routine with a buffer size limit of zero. [Kevin Corry, Alasdair Kergon]
-
Andrew Morton authored
From: Kevin Corry <kevcorry@us.ibm.com> Clarify the comment regarding the "next" field in struct dm_target_spec. The "next" field has different behavior if you're performing a DM_TABLE_STATUS command than it does if you're performing a DM_TABLE_LOAD command. See populate_table() and retrieve_status() in drivers/md/dm-ioctl.c for more details on how this field is used.
-
Andrew Morton authored
From: Kevin Corry <kevcorry@us.ibm.com> Correctly align the dm_target_spec structures during retrieve_status().
-
Andrew Morton authored
From: Kevin Corry <kevcorry@us.ibm.com> Log an error if the target has unknown target type, or zero length.
-
Andrew Morton authored
From: Kevin Corry <kevcorry@us.ibm.com> dm.c: Use wake_up() rather than wake_up_interruptible() with the eventq.
-
Andrew Morton authored
From: Kevin Corry <kevcorry@us.ibm.com> Handle interrupts within suspend.
-
Andrew Morton authored
From: Kevin Corry <kevcorry@us.ibm.com> Check the uptodate flag in sub-bios to see if there was an error. [Mike Christie]
-
Andrew Morton authored
From: Kevin Corry <kevcorry@us.ibm.com> Fix 64/32 bit ioctl problems.
-
Petr Vandrovec authored
The recent controlling terminal changes broke exec from multithreaded application because de_thread was not upgraded to new arrangement. I know that I should not have LD_PRELOAD library which automatically creates one thread, but it looked like a cool solution to the problem I had. de_thread must initialize the controlling terminal information in the new thread group.
-
- 16 Apr, 2004 25 commits
-
-
Linus Torvalds authored
-
Linus Torvalds authored
-
Linus Torvalds authored
-
Marcel Holtmann authored
The just merged openpromfs remount patch contains a silly typo in the field of the super_operations structure. Fixed like this.
-
bk://gkernel.bkbits.net/misc-2.6Linus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
bk://gkernel.bkbits.net/net-drivers-2.6Linus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
bk://gkernel.bkbits.net/libata-2.6Linus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
Don Fry authored
When the pcnet32 adapter is installed in a system with long PCI latency and the read burst bit is not set, performance on transmission is very low (under 20Mbit on a 100Mbit link). This patch against 2.6.6-rc1 will make sure that read and write bursts are enabled. Tested on ppc64 and ia32.
-
Jeff Garzik authored
Noticed by Roger Luethi, via-rhine maintainer.
-
Andrew Morton authored
drivers/net/amd8111e.c: In function `amd8111e_vlan_rx': drivers/net/amd8111e.c:677: warning: control reaches end of non-void function
-
Jeff Garzik authored
into redhat.com:/spare/repo/net-drivers-2.6
-
bk://bk.arm.linux.org.uk/linux-2.6-rmkLinus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
Russell King authored
-
Russell King authored
-
Russell King authored
-
Russell King authored
Many binutils versions over the last year appear to silently build assembler files with undefined constants, and able to successfully create executables from such files. The assembler appears to add undefined symbols to the symbol table without any corresponding relocation information. Obviously this is bad news since the resulting executable may not be what the programmer intended. Work around the problem by forcing the linker to fail if there are any undefined symbols in the final object(s).
-
Linus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
Dave Jones authored
If we want to trap NULL vma's, we'd better be sure that we don't dereference it first..
-
Dave Jones authored
Lots of occurences of the same bug..
-
Bartlomiej Zolnierkiewicz authored
From: Meelis Roos <mroos@linux.ee> This is self-explanatory - former SunDisk renamed itself to SanDisk and now there are flash disks with both names.
-
Alexander Viro authored
- we could pass MS_ACTIVE in mount flags and it would be passed into ->get_sb(), leading to interesting failure modes. This flag is only for internal use (it's set once fill_super is complete and reset before the inode eviction on umount); made sure that we never get tricked into having it set it too early.
-
Alexander Viro authored
- a bunch of filesystems force MS_NODIRATIME on mount but forgot to do the same on remount. Fixed.
-
Alexander Viro authored
- a bunch of r/o filesystems did force MS_RDONLY on mount but forgot to do the same on remount. Fixed.
-
Alexander Viro authored
- jff2->remount_fs() was buggy - it played with sb->s_flags instead of doing modifications to *flags (->s_flags will be overwritten using *flags right after the call of ->remount_fs()). Moreover, it tried to do the wrong thing - it should just enforce noatime and be done with that. Fixed, ACKed by maintainer.
-
Alexander Viro authored
- we should force noatime both on mount and remount. Fixed.
-