ChangeSet@1.1394, 2003-07-04 17:53:27-07:00, torvalds@home.osdl.org
When forcing through a signal for some thread-synchronous
event (ie SIGSEGV, SIGFPE etc that happens as a result of a
trap as opposed to an external event), if the signal is
blocked we will not invoce a signal handler, we will just
kill the thread with the signal.
This is equivalent to what we do in the SIG_IGN case: you
cannot ignore or block synchronous signals, and if you try,
we'll just have to kill you.
We don't want to handle endless recursive faults, which the
old behaviour easily led to if the stack was bad, for example.
ChangeSet@1.1393, 2003-07-04 17:24:32-07:00, torvalds@home.osdl.org
Go back to defaulting to 6-byte commands for MODE SENSE,
since some drivers seem to be unhappy about the 10-byte
version.
The subsystem configuration can override this (eg USB or
ide-scsi).
ChangeSet@1.1392, 2003-07-04 17:00:47-07:00, mzyngier@freesurf.fr
[PATCH] EISA: avoid unnecessary probing
- By default, do not try to probe the bus if the mainboard does not
seems to support EISA (allow this behaviour to be changed through a
command-line option).
ChangeSet@1.1391, 2003-07-04 17:00:39-07:00, mzyngier@freesurf.fr
[PATCH] EISA: PCI-EISA dma_mask
- Use parent bridge device dma_mask as default for each discovered
device.
ChangeSet@1.1390, 2003-07-04 17:00:33-07:00, mzyngier@freesurf.fr
[PATCH] EISA: PA-RISC changes
- Probe the right number of EISA slots on PA-RISC. No more, no less.
ChangeSet@1.1389, 2003-07-04 17:00:26-07:00, mzyngier@freesurf.fr
[PATCH] EISA: More EISA ids
ChangeSet@1.1388, 2003-07-04 17:00:19-07:00, mzyngier@freesurf.fr
[PATCH] EISA: Documentation update
ChangeSet@1.1387, 2003-07-04 17:00:12-07:00, mzyngier@freesurf.fr
[PATCH] EISA: core changes
- Now reserves I/O ranges according to EISA specs (four 256 bytes
regions instead of a single 4KB region).
- By default, do not try to probe the bus if the mainboard does not
seems to support EISA (allow this behaviour to be changed through a
command-line option).
- Use parent bridge device dma_mask as default for each discovered
device.
- Allow devices to be enabled or disabled from the kernel command line
(useful for non-x86 platforms where the firmware simply disable
devices it doesn't know about...).
ChangeSet@1.1385, 2003-07-04 14:13:56-07:00, torvalds@home.osdl.org
Carl-Daniel Hailfinger suggest adding a paranoid incoming
trigger as per the "bk help triggers" suggestion, so that
we'll see any new triggers showing up in the tree.
Make it so.
ChangeSet@1.1384, 2003-07-04 12:07:27-07:00, trond.myklebust@fys.uio.no
[PATCH] Use the intents in 'nameidata' to improve NFS close-to-open consistency
- Make use of the open intents to improve close-to-open
cache consistency. Only force data cache revalidation when
we're doing an open().
- Add true exclusive create to NFSv3.
- Optimize away the redundant ->lookup() to check for an
existing file when we know that we're doing NFSv3 exclusive
create.
- Optimize away all ->permission() checks other than those for
path traversal, open(), and sys_access().
ChangeSet@1.1383, 2003-07-04 12:06:43-07:00, trond.myklebust@fys.uio.no
[PATCH] Pass 'nameidata' to ->permission()
- Make the VFS pass the struct nameidata as an optional parameter
to the permission() inode operation.
- Patch may_create()/may_open() so it passes the struct nameidata from
vfs_create()/open_namei() as an argument to permission().
- Add an intent flag for the sys_access() function.
ChangeSet@1.1382, 2003-07-04 12:06:21-07:00, trond.myklebust@fys.uio.no
[PATCH] Pass 'nameidata' to ->create()
- Make the VFS pass the struct nameidata as an optional argument
to the create inode operation.
- Patch vfs_create() to take a struct nameidata as an optional
argument.
ChangeSet@1.1381, 2003-07-04 12:06:06-07:00, trond.myklebust@fys.uio.no
[PATCH] Add open intent information to the 'struct nameidata'
- Add open intent information to the 'struct nameidata'.
- Pass the struct nameidata as an optional parameter to the
lookup() inode operation.
- Pass the struct nameidata as an optional parameter to the
d_revalidate() dentry operation.
- Make link_path_walk() set the LOOKUP_CONTINUE flag in nd->flags instead
of passing it as an extra parameter to d_revalidate().
- Make open_namei(), and sys_uselib() set the open()/create() intent
data.
ChangeSet@1.1380, 2003-07-03 20:23:39-07:00, jgarzik@pobox.com
[PATCH] fix via irq routing
Via irq routing has a funky PIRQD location. I checked my datasheets
and, yep, this is correct all the way back to via686a.
This bug existed for _ages_. I wonder if I created it, even...
ChangeSet@1.1360.1.32, 2003-07-03 19:20:52-07:00, torvalds@home.osdl.org
Re-organize "ext3_get_inode_loc()" and make it easier to
follow by splitting it into two functions: one that calculates
the position, and the other that actually reads the inode
block off the disk.
ChangeSet@1.1360.1.31, 2003-07-03 18:54:42-07:00, torvalds@home.osdl.org
Add an asynchronous buffer read-ahead facility. Nobody
uses it for now, but I needed it for some tuning tests,
and it is potentially useful for others.
ChangeSet@1.1378, 2003-07-03 17:52:16-07:00, greg@kroah.com
Merge kroah.com:/home/linux/BK/bleed-2.5
into kroah.com:/home/linux/BK/pci-2.5
ChangeSet@1.1377, 2003-07-03 17:51:08-07:00, greg@kroah.com
driver core: add my copyright to class.c
ChangeSet@1.1376, 2003-07-03 17:43:49-07:00, greg@kroah.com
[PATCH] driver core: added class_device_rename()
Based on a patch written by Dan Aloni <da-x@gmx.net>
ChangeSet@1.1375, 2003-07-03 17:43:34-07:00, greg@kroah.com
[PATCH] kobject: add kobject_rename()
Based on a patch written by Dan Aloni <da-x@gmx.net>
ChangeSet@1.1374, 2003-07-03 17:43:18-07:00, greg@kroah.com
[PATCH] sysfs: add sysfs_rename_dir()
Based on a patch written by Dan Aloni <da-x@gmx.net>
ChangeSet@1.1373, 2003-07-03 16:39:18-07:00, johnstul@us.ibm.com
[PATCH] jiffies include fix
This patch fixes a bad declaration of jiffies in timer_tsc.c and
timer_cyclone.c, replacing it with the proper usage of jiffies.h.
Caught by gregkh.
ChangeSet@1.1372, 2003-07-03 16:28:49-07:00, greg@kroah.com
[PATCH] SYSFS: add module referencing to sysfs attribute files.
ChangeSet@1.1371, 2003-07-03 16:06:08-07:00, greg@kroah.com
[PATCH] sysfs: change print() to pr_debug() to not annoy everyone.
ChangeSet@1.1370, 2003-07-03 15:52:29-07:00, willy@debian.org
[PATCH] Driver Core: fix firmware binary files
Fixes the sysfs binary file bug.
ChangeSet@1.1369, 2003-07-03 15:52:14-07:00, willy@debian.org
[PATCH] PCI config space in sysfs
- Fix a couple of bugs in sysfs's handling of binary files (my fault).
- Implement pci config space reads and writes in sysfs
ChangeSet@1.1368, 2003-07-03 15:51:59-07:00, willy@debian.org
[PATCH] PCI: arch/i386/pci/legacy.c: use raw_pci_ops
Make pcibios_fixup_peer_bridges() use raw_pci_ops directly instead of
faking pci_bus and pci_dev.
ChangeSet@1.1367, 2003-07-03 15:51:45-07:00, willy@debian.org
[PATCH] PCI: arch/i386/pci/irq.c should use pci_find_bus
Use pci_find_bus rather than relying on the return value of pci_scan_bus.
ChangeSet@1.1366, 2003-07-03 15:51:30-07:00, willy@debian.org
[PATCH] PCI: Remove pci_bus_exists
Convert all callers of pci_bus_exists() to call pci_find_bus() instead.
Since all callers of pci_find_bus() are __init or __devinit, mark it as
__devinit too.
ChangeSet@1.1365, 2003-07-03 15:51:15-07:00, willy@debian.org
[PATCH] PCI: pci_find_bus needs a domain
Give pci_find_bus a domain argument and move its declaration to <linux/pci.h>
ChangeSet@1.1364, 2003-07-03 15:50:59-07:00, willy@debian.org
[PATCH] PCI: arch/i386/pci/direct.c can use __init, not __devinit
pci_sanity_check() is only called from functions marked __init, so it
can be __init too.
ChangeSet@1.1363, 2003-07-03 15:50:39-07:00, willy@debian.org
[PATCH] PCI: Improve documentation
Fix some grammar problems
Add a note about Fast Back to Back support
Change the slot_name recommendation to pci_name().
ChangeSet@1.1360.2.3, 2003-07-03 15:45:44+00:00, ambx1@neo.rr.com
[PNP] Fix manual resource setting API
This patch corrects a trivial thinko in the manual resource api.
ChangeSet@1.1360.2.2, 2003-07-03 15:42:36+00:00, ambx1@neo.rr.com
[PNP] Allow resource auto config to assign disabled resources
This patch updates the resource manager so that it actually assigns
disabled resources when they are requested by the device.
ChangeSet@1.1360.2.1, 2003-07-03 15:39:09+00:00, ambx1@neo.rr.com
[PNP] Handle Disabled Resources Properly
Some devices will allow for individual resources to be disabled,
even when the device as a whole is active. The current PnP
resource manager is not handling this situation properly. This
patch corrects the issue by detecting disabled resources and then
flagging them. The pnp layer will now skip over any disabled
resources. Interface updates have also been included so that we
can properly display resource tables when a resource is disabled.
Also note that a new flag "IORESOURCE_DISABLED" has been added to
linux/ioports.h.
ChangeSet@1.1360.1.29, 2003-07-03 00:39:31-07:00, torvalds@home.osdl.org
The sbp2 driver needs <linux/pci.h>, but didn't include it. It apparently
used to work due to some random magic indirect include, but broke lately.
Do the obvious fix.
ChangeSet@1.1360.1.28, 2003-07-03 00:38:29-07:00, rusty@rustcorp.com.au
[PATCH] Make ksoftirqd a normal per-cpu variable.
This moves the ksoftirqd pointers out of the irq_stat struct, and uses a
normal per-cpu variable. It's not that time critical, nor referenced in
assembler. This moves us closer to making irq_stat a per-cpu variable.
Because some archs have hardcoded asm references to offsets in this
structure, I haven't touched non-x86. The __ksoftirqd_task field is
unused in other archs, too.
ChangeSet@1.1360.1.27, 2003-07-03 00:38:21-07:00, rusty@rustcorp.com.au
[PATCH] Remove unused __syscall_count
Noone seems to use __syscall_count. Remove the field from i386
irq_cpustat_t struct, and the generic accessor macros.
Because some archs have hardcoded asm references to offsets in this
structure, I haven't touched non-x86, but doing so is usually
trivial.
ChangeSet@1.1360.1.26, 2003-07-03 00:32:57-07:00, rusty@rustcorp.com.au
[PATCH] Per-cpu variable in mm/slab.c
Rather trivial conversion. Tested on SMP.
ChangeSet@1.1360.1.25, 2003-07-03 00:32:49-07:00, rusty@rustcorp.com.au
[PATCH] Remove cpu arg from cpu_raise_irq
The function cpu_raise_softirq() takes a softirq number, and a cpu number,
but cannot be used with cpu != smp_processor_id(), because there's no
locking around the pending softirq lists. Since noone does this, remove
that arg.
As per Linus' suggestion, names changed:
raise_softirq(int nr)
cpu_raise_softirq(int cpu, int nr) -> raise_softirq_irqoff(int nr)
__cpu_raise_softirq(int cpu, int nr) -> __raise_softirq_irqoff(int nr)
ChangeSet@1.1360.1.24, 2003-07-02 22:50:27-07:00, akpm@osdl.org
[PATCH] e100 use-after-free fix
I though Scott had recently merged this but it seems not. We'll be
needing this patch if you merge Manfred's page unmapping debug patch.
ChangeSet@1.1360.1.23, 2003-07-02 22:50:19-07:00, akpm@osdl.org
[PATCH] Fix cciss hang
From: Jens Axboe <axboe@suse.de>
It fixes a hang when performing large I/O's. Has been tested and acked by
the maintainer, "Wiran, Francis" <francis.wiran@hp.com>.
ChangeSet@1.1360.1.22, 2003-07-02 22:50:11-07:00, akpm@osdl.org
[PATCH] Set limits on CONFIG_LOG_BUF_SHIFT
From: bert hubert <ahu@ds9a.nl>
Attached patch adds a range check to LOG_BUF_SHIFT and clarifies the
configuration somewhat. I managed to build a non-booting kernel because I
thought 64 was a nice power of two, which lead to the kernel blocking when
it tried to actually use or allocate a 2^64 buffer.
ChangeSet@1.1360.1.21, 2003-07-02 22:50:04-07:00, akpm@osdl.org
[PATCH] ext3: fix journal_release_buffer() race
CPU0 CPU1
journal_get_write_access(bh)
(Add buffer to t_reserved_list)
journal_get_write_access(bh)
(It's already on t_reserved_list:
nothing to do)
(We decide we don't want to
journal the buffer after all)
journal_release_buffer()
(It gets pulled off the transaction)
journal_dirty_metadata()
(The buffer isn't on the reserved
list! The kernel explodes)
Simple fix: just leave the buffer on t_reserved_list in
journal_release_buffer(). If nobody ends up claiming the buffer then it will
get thrown away at start of transaction commit.
ChangeSet@1.1360.1.20, 2003-07-02 22:49:50-07:00, akpm@osdl.org
[PATCH] fix double mmdrop() on exec path
If load_elf_binary() (and the other binary handlers) fail after
flush_old_exec() (for example, in setup_arg_pages()) then do_execve() will go
through and do mmdrop(bprm.mm).
But bprm.mm is now current->mm. We've just freed the current process's mm.
The kernel dies in a most ghastly manner.
Fix that up by nulling out bprm.mm in flush_old_exec(), at the point where we
consumed the mm. Handle the null pointer in the do_execve() error path.
Also: don't open-code free_arg_pages() in do_execve(): call it instead.
ChangeSet@1.1360.1.19, 2003-07-02 22:49:43-07:00, akpm@osdl.org
[PATCH] ext2: inode allocation race fix
ext2's inode allocator will call find_group_orlov(), which will return a
suitable blockgroup in which the inode should be allocated. But by the time
we actually try to allocate an inode in the blockgroup, other CPUs could have
used them all up.
ext2 will bogusly fail with "ext2_new_inode: Free inodes count corrupted in
group NN".
To fix this we just advance onto the next blockgroup if the rare race
happens. If we've scanned all blockgroups then return -ENOSPC.
(This is a bit inaccurate: after we've scanned all blockgroups, there may
still be available inodes due to inode freeing activity in other blockgroups.
This cannot be fixed without fs-wide locking. The effect is a slightly
early ENOSPC in a nearly-full filesystem).
ChangeSet@1.1360.1.18, 2003-07-02 22:49:35-07:00, akpm@osdl.org
[PATCH] Security hook for vm_enough_memory
From: Stephen Smalley <sds@epoch.ncsc.mil>
This patch against 2.5.73 replaces vm_enough_memory with a security hook
per Alan Cox's suggestion so that security modules can completely replace
the logic if desired.
Note that the patch changes the interface to follow the convention of the
other security hooks, i.e. return 0 if ok or -errno on failure (-ENOMEM in
this case) rather than returning a boolean. It also exports various
variables and functions required for the vm_enough_memory logic.
ChangeSet@1.1360.1.17, 2003-07-02 22:49:26-07:00, akpm@osdl.org
[PATCH] cleanup and generalise lowmem_page_address
From: William Lee Irwin III <wli@holomorphy.com>
This patch allows architectures to micro-optimize lowmem_page_address() at
their whims. Roman Zippel originally wrote and/or suggested this back when
dependencies on page->virtual existing were being shaken out. That's
long-settled, so it's fine to do this now.
ChangeSet@1.1360.1.16, 2003-07-02 22:49:14-07:00, akpm@osdl.org
[PATCH] fix lost-tick compensation corner-case
From: john stultz <johnstul@us.ibm.com>
This patch catches a corner case in the lost-tick compensation code.
There is a check to see if we overflowed between reads of the two time
sources, however should the high res time source be slightly slower then
what we calibrated, its possible to trigger this code when no ticks have
been lost.
This patch adds an extra check to insure we have seen more then one tick
before we check for this overflow. This seems to resolve the remaining
"time doubling" issues that I've seen reported.
ChangeSet@1.1360.1.15, 2003-07-02 22:49:07-07:00, akpm@osdl.org
[PATCH] fix lost_tick detector for speedstep
From: john stultz <johnstul@us.ibm.com>
The patch tries to resolve issues caused by running the TSC based lost
tick compensation code on CPUs that change frequency (speedstep, etc).
Should the CPU be in slow mode when calibrate_tsc() executes, the kernel
will assume we have so many cycles per tick. Later when the cpu speeds up,
the kernel will start noting that too many cycles have past since the last
interrupt. Since this can occasionally happen, the lost tick compensation
code then tries to fix this by incrementing jiffies. Thus every tick we
end up incrementing jiffies many times, causing timers to expire too
quickly and time to rush ahead.
This patch detects when there has been 100 consecutive interrupts where we
had to compensate for lost ticks. If this occurs, we spit out a warning
and fall back to using the PIT as a time source.
I've tested this on my speedstep enabled laptop with success, and others
laptop users seeing this problem have reported it works for them. Also to
ensure we don't fall back to the slower PIT too quickly, I tested the code
on a system I have that looses ~30 ticks about every second and it can
still manage to use the TSC as a good time source.
This solves most of the "time doubling" problems seen on laptops.
Additionally this revision has been modified to use the cleanups made in
rename-timer_A1.
ChangeSet@1.1360.1.14, 2003-07-02 22:48:59-07:00, akpm@osdl.org
[PATCH] timer renaming and cleanups
From: john stultz <johnstul@us.ibm.com>
This renames the bad "timer" variable to "cur_timer" and moves externs to
.h files.
ChangeSet@1.1360.1.13, 2003-07-02 22:48:52-07:00, akpm@osdl.org
[PATCH] Report detached thread exit to the debugger
From: Daniel Jacobowitz <dan@debian.org>
Right now, CLONE_DETACHED threads silently vanish from GDB's sight when
they exit. This patch lets the thread report its exit to the debugger, and
then be auto-reaped as soon as it is collected, instead of being reaped as
soon as it exits and not reported at all.
GDB works either way, but this is more correct and will be useful for some
later GDB patches.
ChangeSet@1.1360.1.12, 2003-07-02 22:48:41-07:00, akpm@osdl.org
[PATCH] Make CONFIG_TC35815 depend on CONFIG_TOSHIBA_JMR3927
From: Adrian Bunk <bunk@fs.tum.de>
I got an error at the final linking with CONFIG_TC35815 enabled since
the variables tc_readl and tc_writel are not available.
The only place where they are defined is arch/mips/pci/ops-jmr3927.c.
ChangeSet@1.1360.1.11, 2003-07-02 22:48:33-07:00, akpm@osdl.org
[PATCH] block_llseek(): remove lock_kernel()
Replace it with the blockdev inode's i_sem. And we only really need that for
atomic access to file->f_pos.
ChangeSet@1.1360.1.10, 2003-07-02 22:48:26-07:00, akpm@osdl.org
[PATCH] remove lock_kernel() from file_ops.flush()
Rework the file_ops.flush() API sothat it is no longer called under
lock_kernel(). Push lock_kernel() down to all impementations except CIFS,
which doesn't want it.
ChangeSet@1.1360.1.9, 2003-07-02 22:48:18-07:00, akpm@osdl.org
[PATCH] procfs: remove some unneeded lock_kernel()s
From: William Lee Irwin III <wli@holomorphy.com>
Remove spurious BKL acquisitions in /proc/. The BKL is not required to
access nr_threads for reporting, and get_locks_status() takes it
internally, wrapping all operations with it.
ChangeSet@1.1360.1.8, 2003-07-02 22:48:06-07:00, akpm@osdl.org
[PATCH] nommu vmtruncate: remove lock_kernel()
lock_kernel() need not be held across truncate.
ChangeSet@1.1360.1.7, 2003-07-02 22:47:59-07:00, akpm@osdl.org
[PATCH] inode_change_ok(): remove lock_kernel()
`attr' is on the stack, and the inode's contents can change as soon as we
return from inode_change_ok() anyway. I can't see anything which is actually
being locked in there.
ChangeSet@1.1360.1.6, 2003-07-02 22:47:51-07:00, akpm@osdl.org
[PATCH] ramfs: use rgeneric_file_llseek
Teach ramfs to use generic_file_llseek: default_llseek takes lock_kernel().
ChangeSet@1.1360.1.5, 2003-07-02 22:47:43-07:00, akpm@osdl.org
[PATCH] NUMA memory reporting fix
From: Dave Hansen <haveblue@us.ibm.com>
The current numa meminfo code exports (via sysfs) pgdat->node_size, as
totalram. This variable is consistently used elsewhere to mean "the number
of physical pages that this particular node spans". This is _not_ what we
want to see from meminfo, which is: "how much actual memory does this node
have?"
The following patch removes pgdat->node_size, and replaces it with
->node_spanned_pages. This is to avoid confusion with a new variable,
node_present_pages, which is the _actual_ value that we want to export in
meminfo. Most of the patch is a simple s/node_size/node_spanned_pages/.
The node_size() macro is also removed, and replaced with new ones for
node_{spanned,present}_pages() to avoid confusion.
We were bitten by this problem in this bug:
http://bugme.osdl.org/show_bug.cgi?id=818
Compiled and tested on NUMA-Q.
ChangeSet@1.1360.1.4, 2003-07-02 22:47:30-07:00, akpm@osdl.org
[PATCH] page unmapping debug
From: Manfred Spraul <manfred@colorfullife.com>
Manfred's latest page unmapping debug patch.
The patch adds support for a special debug mode to both the page and the slab
allocator: Unused pages are removed from the kernel linear mapping. This
means that now any access to freed memory will cause an immediate exception.
Right now, read accesses remain totally unnoticed and write accesses may be
catched by the slab poisoning, but usually far too late for a meaningfull bug
report.
The implementation is based on a new arch dependant function,
kernel_map_pages(), that removes the pages from the linear mapping. It's
right now only implemented for i386.
Changelog:
- Add kernel_map_pages() for i386, based on change_page_attr. If
DEBUG_PAGEALLOC is not set, then the function is an empty stub. The stub
is in <linux/mm.h>, i.e. it exists for all archs.
- Make change_page_attr irq safe. Note that it's not fully irq safe due to
the lack of the tlb flush ipi, but it's good enough for kernel_map_pages().
Another problem is that kernel_map_pages is not permitted to fail, thus
PSE is disabled if DEBUG_PAGEALLOC is enabled
- use kernel_map pages for the page allocator.
- use kernel_map_pages for the slab allocator.
I couldn't resist and added additional debugging support into mm/slab.c:
* at kfree time, the complete backtrace of the kfree caller is stored
in the freed object.
* a ptrinfo() function that dumps all known data about a kernel virtual
address: the pte value, if it belongs to a slab cache the cache name and
additional info.
* merging of common code: new helper function obj_dbglen and obj_dbghdr
for the conversion between the user visible object pointers/len and the
actual, internal addresses and len values.
ChangeSet@1.1360.1.3, 2003-07-02 22:47:23-07:00, akpm@osdl.org
[PATCH] move_vma() make_pages_present() fix
From: Hugh Dickins <hugh@veritas.com>
mremap's move_vma VM_LOCKED case was still wrong.
If the do_munmap unmaps a part of new_vma, then its vm_start and vm_end
from before cannot both be the right addresses for the make_pages_present
range, and may BUG() there.
We need [new_addr, new_addr+new_len) to be locked down; but
move_page_tables already transferred the locked pages [new_addr,
new_addr+old_len), and they're either held in a VM_LOCKED vma throughout,
or temporarily in no vma: in neither case can be swapped out, so no need to
run over that range again.
ChangeSet@1.1360.1.2, 2003-07-02 16:02:30-07:00, ilmari@ilmari.org
[PATCH] Allow modular DM
With the recent fixes, io_schedule needs to be exported for modular dm
to work.
ChangeSet@1.1360.1.1, 2003-07-02 11:16:48-07:00, torvalds@home.osdl.org
Linux 2.5.74
TAG: v2.5.74