- 09 Apr, 2003 12 commits
-
-
David S. Miller authored
into kernel.bkbits.net:/home/davem/net-2.5
-
David S. Miller authored
-
David S. Miller authored
-
David S. Miller authored
-
David S. Miller authored
into nuts.ninka.net:/home/davem/src/BK/net-2.5
-
Linus Torvalds authored
-
Linus Torvalds authored
-
Linus Torvalds authored
-
Linus Torvalds authored
-
Rusty Russell authored
-
Linus Torvalds authored
on the list-head being at the top of the DRI data structures and using hard casts.
-
bk://linux-dj.bkbits.net/agpgartLinus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
- 10 Apr, 2003 9 commits
-
-
Dave Jones authored
-
Dave Jones authored
All the other GART drivers display what they've found, so make this one follow suit.
-
Dave Jones authored
Offering the K7 GARTs on 64bit kernels causes sillyness, like reports of "unrecognised device, try unsupported". We don't want people to even try that, so don't offer it in the first place. There's really no good reason for offering any of the IA32 era GARTs on a x86-64 64bit kernel. If Intel (or whoever) ever do an x86-64 clone, a new gart driver will be started anyways, as has been done for amd-k8-agp.
-
Dave Jones authored
This optioned saved just a handful of bytes, and uglied up the code quite a lot. Saving less than a page of memory is not as important as maintainable code.
-
Dave Jones authored
-
Dave Jones authored
into tetrachloride.(none):/mnt/raid/src/kernel/2.5/agpgart
-
Dave Jones authored
-
Dave Jones authored
-
Dave Jones authored
Also includes various other fixes from Matt Tolentino
-
- 09 Apr, 2003 19 commits
-
-
Linus Torvalds authored
- bad preprocessor test always tested true, even when it shouldn't. - annotate user pointers with proper annotations. Both found by my automatic type checker tool.
-
Linus Torvalds authored
-
Linus Torvalds authored
-
Linus Torvalds authored
-
Linus Torvalds authored
-
Linus Torvalds authored
-
Linus Torvalds authored
-
Hideaki Yoshifuji authored
-
Stephen Hemminger authored
-
http://lia64.bkbits.net/to-linus-2.5Linus Torvalds authored
into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux
-
David Mosberger authored
-
Linus Torvalds authored
type evaluation. This tags the system call interfaces in fs/open.c, fs/dcache.c and mm/swapfile.c - and tags the path walking helper functions.
-
Andrew Morton authored
It can miss an fput() if passed the fd of a file which has no ->mapping.
-
Andrew Morton authored
From: Marc Zyngier <mzyngier@freesurf.fr> The included patch helps 3c59x to display the correct identification string (3c592 and 3c597 were displayed as 3c590). It also gets rid of the EISA_bus reference, which is not needed anymore since the driver has been ported to the EISA probing API.
-
Andrew Morton authored
From: Manfred Spraul <manfred@colorfullife.com> Update and clarify the incorrect commentary around task_lock()
-
Andrew Morton authored
From: "Martin J. Bligh" <mbligh@aracnet.com> Fix the commentary around the address_space fields.
-
Andrew Morton authored
MS_ASYNC will currently wait on previously-submitted I/O, then start new I/O and not wait on it. This can cause undesirable blocking if msync is called rapidly against the same memory. So instead, change msync(MS_ASYNC) to not start any IO at all. Just flush the pte dirty bits into the pageframe and leave it at that. The IO _will_ happen within a kupdate period. And the application can use fsync() or fadvise(FADV_DONTNEED) if it actually wants to schedule the IO immediately. (This has triggered an ext3 bug - the page's buffers get dirtied so fast that kjournald keeps writing the buffers over and over for 10-20 seconds before deciding to give up for some reason)
-
Andrew Morton authored
From: Andreas Gruenbacher <agruen@suse.de> Missing brelse() in ext2/ext3 extended attribute code The ext2 and ext3 EA implementations fail to release a buffer_head if the inode that is being accessed is sharing EAs with another inode, and an attribute is set to the same value that it has already, like so: $ touch f g $ setfattr -n user.test -v test f g # (Now, both f and g refer to the same EA block.) $ setfattr -n user.test -v test f With the bug, an "invalidate: busy buffer" or "invalidate: dirty buffer" message will be logged when the file system is unmounted. This patch fixes the problem. At the implementation level: The code was assuming that ext3_xattr_cache_find cannot return the same block the inode already is associated with, so testing for (old_bh != new_bh) would determine whether the old block is resued or an additional bh is held. This is wrong if the EA block is used by multiple inodes (in which case it stays in the cache), and the block isn't actually modified. Instead of testing for (old_bh != new_bh), the code now does a get_bh() in the branch that keeps the old block, which assures that new_bh now is either NULL or a handle that must be released at the end of ext3_xattr_set_handle2().
-
Andrew Morton authored
From: Davide Libenzi <davidel@xmailserver.org> This fixes a bug that might happen having a thread doing epoll_wait() with another thread doing epoll_ctl(EPOLL_CTL_DEL) and close(). The fast check inside eventpoll_release() is good to not effect performace of code not using epoll, but it requires get_file() to be called ( that can be avoided by dropping the fast check ). I opted to keep the fast check and to have epoll to call get_file() before the event send loop. I tested it on UP and 2SMP with a bug-exploiting program provided by @pivia.com ( thx to them ) and it looks fine. I also update the 2.4.20 epoll patch with this fix :
-