- 17 Apr, 2004 1 commit
-
-
Pavel Roskin authored
Patch from: Pavel Roskin As it turns out, mixing MODULE_PARM and module_param in one module is wrong. The parameters specified in module_param are ignored. I've just posted a patch to LKML that will detect this condition and warn about it. The new debugging code used the new-style module_param, which means that all instances of MODULE_PARM should be converted. The attached patch does that. An additional bonus is that module_param_array provides the number of array elements. This allowed me to change tcic.c and i82365.c to use this number for IRQ list. This change was tested with i82365. If "irq_list" is not specified, irq_list_count is 0. I set all permissions to 0444 to be safe. I think we have no secrets from the users regarding those parameters. If some parameters can be changed safely at the runtime, the permissions could be changed to 0644. I didn't examine how safe (and how useful) it would be, so it's 0444 for now.
-
- 16 Apr, 2004 32 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.
-
Alexander Viro authored
- same problem as with sysv - mount-time checks for fs being good for writing are absent on remount. Check added.
-
Alexander Viro authored
- several variants of sysv fs are supported only r/o. Driver does force r/o on mount, but doesn't do anything on remount. As the result, one can remount them r/w and results are Not Pretty(tm). Missing checks added, code cleaned up. - we had double-brelse() in v7fs - if sanity checks on root inode will succeed, but allocation of root dentry fails, we brelse() the same buffer_head twice. Fixed.
-
David S. Miller authored
into nuts.davemloft.net:/disk1/BK/tg3-2.6
-
David S. Miller authored
-
David S. Miller authored
into nuts.davemloft.net:/disk1/BK/net-2.6
-
David S. Miller authored
-
Linus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
- 15 Apr, 2004 7 commits
-
-
bk://bk.linux1394.org/ieee1394-2.6Linus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
-
Benjamin Herrenschmidt authored
The low level kernel interface to RTAS (the firmware runtime services) was plagued with races that could cause from bogus results of RTAS operations to total machine crashes in some circumstances. This patch fix the ones I could identify, hoping I didn't miss any. I also added a WARN_ON (well, it's asm equivalent) to enter_rtas to make sure we never _ever_ try to call that with interrupts enabled.
-
Anton Blanchard authored
This fix comes from ppc32. Always initialise dn->type and dn->name so that code doesnt have to check for NULL everywhere. There is at least one bug report where we oopsed because of this.
-
Anton Blanchard authored
We have been debugging some strange fails where we branch to 0 in real mode. At the moment this results in the cpu running through the initialisation code and failing somewhere well into it. The following patch uses the featuring nop'ing code to remove the branch at real address 0 so it falls through to a trap instruction and gets caught early.
-
Adam Goode authored
This adda nmi_watchdog=2 support to the Pentium M processor. The P-M is a P6 chip, but it shares some chipset logic with the Pentium 4, so it requires this workaround to function. Without this patch, NMI gets stuck after 1 count. With it, the NMI fires and breaks me out of UHCI-related hard lockups. This patch is basically a modified version of the same patch for oprofile. See the threaded discussion here: http://lkml.org/lkml/2004/2/12/181
-
David S. Miller authored
-