| Age | Commit message (Collapse) | Author |
|---|
|
- generic_file_open() comment fix (Bill Irwin)
- kerneldoc fix in truncate.c (Aniruddha M Marathe)
- remove truncate debug check.
- page_lock comment fix (Robert Love)
- remove unused device mapper label.
- 3c509 docco fix ("Mark Tranchant" <mark@tranchant.freeserve.co.uk>)
--
Documentation/networking/3c509.txt | 2 +-
drivers/md/dm-ioctl.c | 1 -
fs/open.c | 2 +-
include/linux/fs.h | 2 +-
mm/truncate.c | 8 +++-----
5 files changed, 6 insertions(+), 9 deletions(-)
|
|
This is what a lot of the callers really wanted.
|
|
into kernel.bkbits.net:/home/davem/net-2.5
|
|
|
|
|
|
into kernel.bkbits.net:/home/davem/net-2.5
|
|
|
|
into nuts.ninka.net:/home/davem/src/BK/net-2.5
|
|
|
|
|
|
Also use kernel-doc for struct cycx_hw
|
|
|
|
|
|
net_device
|
|
|
|
into nuts.ninka.net:/home/davem/src/BK/net-2.5
|
|
into nuts.ninka.net:/home/davem/src/BK/net-2.5
|
|
into nuts.ninka.net:/home/davem/src/BK/net-2.5
|
|
into nuts.ninka.net:/home/davem/src/BK/net-2.5
|
|
into nuts.ninka.net:/home/davem/src/BK/net-2.5
|
|
|
|
|
|
into osdl.org:/home/mochel/src/kernel/devel/linux-2.5-core
|
|
This way, we can easily handle devices that contain an arbitrary number of
resources reported by the platform.
|
|
This is a bit neater.
|
|
into osdl.org:/home/mochel/src/kernel/devel/linux-2.5-core
|
|
From: Christoph Hellwig <hch@lst.de>
Remove smp.h leftovers. From the ia64 tree.
|
|
From: Petr Vandrovec <vandrove@vc.cvut.cz>
While I was trying to hunt down problem with spin_lock_irq in
send_sig_info, I noticed that debugging spinlocks are a bit unusable.
The problem is that these spinlocks first print warning, and then
decrement babble. So if the lock is used by printk code (like runqueue
lock was), we get nothing, just a lockup or a double fault... When we
first decrement babble and then print the error message we can break
this unfortunate situation and the error message (5 of the same...)
appear on screen.
|
|
put_dirty_page() currently assumes PAGE_COPY for the stack page's ptes. But
for x86_64 (at least) this is not the case.
The patch adds the extra arg to put_dirty_page(), updates all callers and fixes
x86_64.
|
|
From Russell King:
The location and interrupt of some platform devices are only known by
platform specific code. In order to avoid putting platform specific
parameters into drivers, place resource and irq members into struct
platform_device.
|
|
Originally from Matt Dobson. I've been running with this for a while
in -dj, with no noticable side-effects.
Matt:
node_zonelists looks like it should really be declared of size
MAX_NR_ZONES, not GFP_ZONEMASK. GFP_ZONEMASK is currently 15, making
node_zonelists an array of 16 elements. The extra zonelists are all
just duplicates of the *real* zonelists, namely the first 3 entries.
Again, if anyone can explain to me why I'm wrong in my thinking, I'd
love to know. There's certainly no way you could bitwise-and something
with any combination of the GFP_DMA and GFP_HIGHMEM flags to refer to
the 12th zonelist or some such! Or am I crazy?
|
|
Add bio traversal functionality. This is a prereq for doing ide
multiwrites safely and sanely. Patch was originally done by Suparna,
Bartlomiej picked it up and changed the design somewhat. From Bart:
Main idea is now reversed - instead of introducing rq->hard_bio as
pointer for bio to be completed and using rq->bio as pointer for bio
to be submitted, rq->cbio is introduced for submissions and rq->bio
is used for completions
This minimizes changes to block layer and assures that all existing
block users are not affected by this patch.
|
|
From Ben Collins.
|
|
into kernel.bkbits.net:/home/davem/net-2.5
|
|
|
|
Much help provided by Rusty Russell in fixing device leak
and TOS modification handling bugs.
|
|
Patch from "Theodore Ts'o" <tytso@mit.edu>
We now use 0x7ffffff as the EOF cookie, because Linux NFS stupidly interprets
the cookie (which is supposed to be a bag of bits without necessarily any
semantic value) as a signed 64 bit integer, and then converts it to a
unsigned integer, and then blows up if it cannot be expressed be expressed as
a 32-bit value!!
In order to do this, we have to fold the hash value 0x7ffffff into the hash
value 0x7ffffffe. This is relatively safe; the only time we will lose if the
directory contains filenames that hash to both 0x7ffffffe and 0x7fffffff
(under the original hash), and the last directory entry which hashes to
0x7ffffffe is at the end of a leaf block, and the first directory entry which
hashes to 0x7fffffff is at the beginning of a leaf block.
|
|
exit_mmap() currently assumes that the exitting task used virtual address
span TASK_SIZE.
But on some platforms, TASK_SIZE is variable, based on current->mm.
But exit_mmap() can be called from (say) procfs's call to mmput. In which
case current->mm has nothing to do with the mm which is being put in
mmput().
So rather than assuming that the mm which is being put is current->mm, we
need to calculate the virtual span of the mm. Add a new per-arch macro
MM_VM_SIZE() for that.
Some platforms can currently go BUG over this (where?). sparc64 is safe
because our TASK_SIZE is constant.
Platforms such as ia64 should stick the VM extent inside of mm_struct, I'd
suggest adding it to mm_context_t.
1) TASK_SIZE means what is valid for mmap()'s in the processes
address space
2) MM_VM_SIZE means where things might be mapped for a MM, including
private implementation-specific areas created by the kernel
which the user cannot access
|
|
From: Zwane Mwaikambo <zwane@linuxpower.ca>
The proc interface has no way of telling wether there is an active cpufreq
driver or not. This means that if you don't have a cpufreq supported
processor, this will oops in various possible places.
|
|
From: Bjorn Stenberg <bjorn@haxx.se>
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
This simple patch makes the linux fat filesystem driver use the
next_cluster field in the fat_boot_fsinfo structure. This field is a hint
where to start looking for free clusters.
Using this field makes a big difference for disks connected over slow links
such as USB 1.1. Finding the first free cluster on a 40gig fat-formatted
usb disk can today take several minutes. This patch cuts it down to a
fraction of a second.
Also, commit the next_cluster search hint toand from the superblock in
write_super/fill_super.
|
|
From: Christoph Hellwig <hch@lst.de>
Whee! devfs_register isn't used anymore in the whole tree and with
it some other devfs crap. Kill it for good.
|
|
From: Rusty Russell <rusty@rustcorp.com.au>, David Mosberger
The patch below updates the other platforms with module_arch_cleanup().
Also, I added more debug output to kernel/module.c since I found it useful
to be able to see the final section layout.
|
|
Here are three more fixes which I missed in the previous patch.
|
|
Don't depend on undefined preprocessor symbols evaluating to zero.
|
|
into home.transmeta.com:/home/torvalds/v2.5/linux
|
|
|
|
|
|
into nuts.ninka.net:/home/davem/src/BK/net-2.5
|
|
into osdl.org:/home/mochel/src/kernel/devel/linux-2.5-core
|
|
There is a _lot_ of stuff in linux/elf.h that shouldn't be there.
This moves the arch-specific stuff in linux/elf.h into the corresponding
asm header files.
|
