- 03 Apr, 2002 23 commits
-
-
Dave Jones authored
-
Dave Jones authored
Originally from Anton Altaparmakov.. This causes errors from get_block() in block_read_full_page() to be detected and handled properly (by setting page error flag). Without the patch the page (or parts of the page) will contain random data on get_block() failing without any form of error being signalled which can be catastrophic for filesystems using block_read_full_page() for accessing their metadata. And for normal data it would mean the user would see random data instead of what they expected.
-
Dave Jones authored
-
Dave Jones authored
-
Dave Jones authored
Various quirks from 2.4 and other sources.
-
Dave Jones authored
Another 2.4 forward port, original from Andrew Morton.
-
Dave Jones authored
-
Dave Jones authored
These files use completion, but don't include header.
-
Dave Jones authored
-
Dave Jones authored
Another small change from 2.4
-
Dave Jones authored
Add support for AMD Elan. (More ELAN patches to follow which rely on CONFIG_MELAN)
-
Dave Jones authored
Another forward port from 2.4
-
Dave Jones authored
-
Dave Jones authored
-
Adam Radford authored
Self explanatory driver update from vendor.
-
Dave Jones authored
Support for an extra interrupt router.
-
Dave Jones authored
introduction of ALSA moved some files around. This updates various references.
-
Dave Jones authored
EFI GUID partition table support from Matt Domsch
-
Dave Jones authored
Clean up capability handling in AGPGart. This came forward from 2.4
-
Greg Kroah-Hartman authored
Here's a very tiny bugfix for arch/i386/kernel/mpparse.c in the 2.4.19-pre2 kernel. It fixes the problem if there is an error in the MP_processor_info() function where the mpc_apicid value is greater than MAX_APICS, then we need to decrement the number of valid processors before we return (the number was just incremented before the check.) The patch was written by James Cleverdon.
-
Dave Jones authored
Simple compile fix.
-
Dave Jones authored
Another from 2.4, see comments for details
-
Dave Hansen authored
Push BKL down to the (few) routines that actually need it, remove it from the do_exit() path.
-
- 02 Apr, 2002 17 commits
-
-
Linus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
David S. Miller authored
ttl of tcp_socket.
-
Linus Torvalds authored
-
Alexander Viro authored
brw_kiovec() and ll_rw_kiovec() switched to struct block_device *.
-
Alexander Viro authored
Bunch of places converted from fsync_dev/invalidate_buffers to fsync_bdev/invalidate_bdev.
-
Alexander Viro authored
get_sb_bdev() stores original block size in ->s_old_blocksize and kill_block_super() restores it. This kills 99% of crap with "oh, I've mounted/umounted that device and its behaviour had changed" (remaining 1% can be dealt in pretty similar ways; ideally I'd like to see ioctls that get/set block size dead and gone).
-
Alexander Viro authored
Fix typo
-
Alexander Viro authored
Use sb_set_blocksize() in JFS instead of trying to do it by hand.
-
Alexander Viro authored
Clean up minix/bitmap.c
-
Alexander Viro authored
Kill BKL in minix/itree* (similar to ext2 patches)
-
Alexander Viro authored
Clean up the write_super-related code in minixfs
-
Alexander Viro authored
Move minix-private stuff to fs/minix/minix.h.
-
Alexander Viro authored
This version of sys_nfsservctl() fix hadn't made DaveM complain.
-
Alexander Viro authored
Obvious romfs fix.
-
Linus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
Linus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
Andrew Morton authored
In 2.5.7 there is a thinko in the allocation and initialisation of the fs-private superblock for ext2. It's passing the wrong type to the sizeof operator (which of course gives the wrong size) when allocating and clearing the memory. Lesson for the day: this is one of the reasons why this idiom: some_type *p; p = malloc(sizeof(*p)); ... memset(p, 0, sizeof(*p)); is preferable to some_type *p; p = malloc(sizeof(some_type)); ... memset(p, 0, sizeof(some_type)); I checked the other filesystems. They're OK (but idiomatically impure). I've added a couple of defensive memsets where they were missing.
-