Russell King [Fri, 2 Jan 2004 19:36:52 +0000 (19:36 +0000)]
[SERIAL] Remove old RSA resource handlign.
The resource handling left in autoconfig() is plainly wrong, since
we've already claimed the necessary resources prior to calling
autoconfig(). Therefore, we remove the superfluous code from
autoconfig().
Andi Kleen [Thu, 1 Jan 2004 03:41:03 +0000 (19:41 -0800)]
[PATCH] X86-64 merge
At least one of them is critical. It fixes an path in the IOMMU that
I broke with the ealier "fullflush" workaround.
- Check for ~/bin/installkernel like i386 (M. Bligh)
- Implement 32bit RTC_IRQ_SET correctly (Lutz Vieweg)
- Disable some useless printks in 32bit emulation
- Warning fixes for mixed C99 style declarations/statements.
- Sync lAPIC power management with i386
- Use topology sysfs like i386
- Fix some serious bugs in the MCE handler. ECC should
be decoded correctly now.
- Add oops=panic option to panic on Oopses.
- Fix hackish code in head.S
- Add missing options in IOMMU
- Fix _syscall6 (Olaf Hering)
- Remove broken ACPI locking code. Port IA64 C version.
- Make safe_smp_processor_id() more reliable
- Read HPET in vsyscall code
- Add workaround for BIOS that corrupt 64bit registers in HLT
- Fix unaligned access in bitops.h
- Remove broken ntp drift correction code for now
- i386 merge in SCI setup
- Fix wrong offset in callin.h (Jim Houston)
- Minor comment fixes
Michael Hunold [Thu, 1 Jan 2004 03:25:24 +0000 (19:25 -0800)]
[PATCH] DVB: Revamp of the TTUSB-DEC driver
- Alter hotplug firmware naming to fit in with dvb standard.
- Use the hotplug firmware loader for 2.6 kernels instead of compiling
the firmware into the module.
- Integrate frontend into ttusb_dec module and remove pseudo-i2c bits,
move ttusb_dec header into source file.
- Rudimentary section filter support (enough for scan).
Michael Hunold [Thu, 1 Jan 2004 03:25:04 +0000 (19:25 -0800)]
[PATCH] DVB: Fixes for frontend drivers
- ves1820: increase mdelay from 30 to 50 to be more reliable with bad
reception quality (Andreas Oberritter)
- dst: remove AUTO_INVERSION for capabilities, allow params
dst_type_flags and dst_type to have multiple values for multiple
cards in one machine (Jamie Honan)
David Mosberger [Wed, 31 Dec 2003 15:18:59 +0000 (07:18 -0800)]
ia64: Allow system-call number to be changed during system-call tracing
(both for native and x86 system call tracing). This is needed
by recent versions of strace and UML likes to do that, too.
David Mosberger [Tue, 30 Dec 2003 17:10:09 +0000 (09:10 -0800)]
ia64: Fix a ptrace-bug that caused "strace -f" to crash the inferior
process. The root-cause of the problem was that ptrace() tried
to copy the portion of the register backing store that landed on
the kernel stack back to users-space, but the resulting state
was inconsistent if the inferior process was in the middle of a
system-call (as would always be the case for strace).
The solution is to avoid all needless copying and to instead
ensure that when accessing a memory location that may belong to
a thread's register-backing store, we attach to that particular
thread, rather than the thread identified by the PID argument.
If the thread happens to be unattachable, we fall back to using
the thread identified by the PID argument. This should have the
desired effect if the thread has terminated already and if the
thread is running while ptrace() is trying to access its state,
all bets are off anyhow and there are no coherency guarantees.
In other words, this should be doing the right thing under all
circumstances.
The patch also fixes the case where PT_AR_BSP and/or PT_CFM are
written while the inferior process is in the middle of a system
call. This makes arguments passed to GDB inferior calls come
out right.
The patch was tested with strace -f and the GDB testsuite, which
showed no regressions compared to the previous version of the
kernel.
Andrew Morton [Tue, 30 Dec 2003 09:00:38 +0000 (01:00 -0800)]
[PATCH] call_usermodehelper retval fix
The reworked firmware loader in the DVB patches needs the fix to the
call_usermodehelper() return value.
From: Rusty Russell <rusty@rustcorp.com.au>
MODULE_ALIAS_BLOCK() and MODULE_ALIAS_CHAR() define aliases of form
"XXX-<major>-<minor>", so we should probe for modules using this form.
Unfortunately in 2.4, block aliases were "XXX-<major>" and char aliases
were of both forms.
Ideally, all modules would now be using MODULE_ALIAS() macros to define
their aliases, and the old configuration files wouldn't matter as much.
Unfortunately, this hasn't happened, so we make request_module() return the
exit status of modprobe, and then do fallback when probing for char and
block devices.
(Kudos to Chris Wright, I stole his kernel_thread flags).
Andrew Morton [Tue, 30 Dec 2003 09:00:07 +0000 (01:00 -0800)]
[PATCH] fix for 16-bit PCMCIA interrupt selection
From: David Hinds <dhinds@sonic.net>
This fixes interrupt allocation for 16-bit PCMCIA cards, so that on systems
supporting ISA bus interrupts, if all ISA interrupts are unavailable, we'll
fall back on sharing the bridge PCI interrupt.
Andrew Morton [Tue, 30 Dec 2003 08:59:37 +0000 (00:59 -0800)]
[PATCH] dhinds is not 2.6 PCMCIA maintainer
From: David Hinds <dhinds@sonic.net>
I have not been actively maintaining PCMCIA for 2.6; I tried asking the
more active developers to see if someone would step into the job but they
were not willing to do so at this time. I'll still submit patches from
time to time.
(David has a ./CREDITS entry, of course).
We should really put in Russell King here, but I'll let him do that
himself.
Andrew Morton [Tue, 30 Dec 2003 08:59:27 +0000 (00:59 -0800)]
[PATCH] PPC32: Fix the mkprep util to work correctly on Solaris 8
From: Tom Rini <trini@kernel.crashing.org>
Peter Wahl <PeterWahl@web.de>
PPC32: Fix the mkprep util to work correctly on Solaris 8.
- There is a very odd problem with the alignment of dword_t values
which causes this program to not work correctly when compiled on
Solaris 8. The workaround is not use a pointer and to memcpy the
values instead.
Andrew Morton [Tue, 30 Dec 2003 07:49:45 +0000 (23:49 -0800)]
[PATCH] readahead: multiple performance fixes
From: Ram Pai <linuxram@us.ibm.com>
I have enclosed a patch that fixes a bunch of performance bugs in the
readahead code.
Below is a brief summary of the problems noticed and the proposed fixes
with some results:
Problem 1: Readahead code closes the readahead window and goes into
slowread path, if a file is accessed the first time at an offset
notequal to zero. In the case of databases(especially in db2), a file
may not be accessed at offset 0 the first time though the i/o's are
sequential.
Fix to Problem 1:
min = get_min_readahead(ra);
orig_next_size = ra-next_size;
- if (ra-next_size == 0 && offset == 0) {
+ if (ra-next_size == 0) {
------------------------------------------------------------------------
Problem 2: After fixing Problem, the readahead window still does not
open up the first time, if all the pages requested are already in the
page cache. This time the window closes because of pagecache hits
instead of misses. To fix this we put in these changes.
------------------------------------------------------------------------
Problem 3: In the case of large random reads, the readahead window is
read in, the moment there is a hit in the active window. And it turns
out that in most of the cases the readahead window gets scrapped,
because the next large random read does not even touch any of the pages
in that readahead window. We fixed this by introducing lazy readahead.
Basically we wait till the last page in the active window gets a hit.
And once the last page is hit, the readahead window is then read in.
This fix gave a tremendous boost in the performance.
To fix this the changes we put in were:
/*
* This read request is within the current window. It is time
* to submit I/O for the ahead window while the application is
* crunching through the current window.
*/
- if (ra-ahead_start == 0) {
+ if (ra-ahead_start == 0 && offset == (ra-start + ra-size -1)) {
------------------------------------------------------------------------
Problem 4:
If the request page does not fall in the active window and is not
the first page of the read ahead window, we scrap both the active
window and the readahaed window and read in the active window. But it
turns out that we read in a lot of pages in the active window based on
the size of the 'projected readahead window size' (the next_size
variable). And we end up using part of the active window and waste the
remaining. We put in a fix where we read in just as many pages in the
active window based on the number of pages used in the recent past.
Again this gave us another big boost in performance and ended up
beating the performance of aio patch on a DSS workload.
The fix to this is:
* ahead window and get some I/O underway for the new
* current window.
*/
+ if (!first_access && preoffset = ra-start &&
+ preoffset < (ra-start + ra-size)) {
+ ra-size = preoffset - ra-start + 2;
+ } else {
+ ra-size = ra-next_size;
------------------------------------------------------------------------
Problem 5:
With all the above fixes there is very low chance that the readahead
window shall close. But however if it does, we found that the slow
read path is really slow. Any loss of sequentiality in the slow read
path is penalized heavily by closing the window back to zero. So we
fixed this by decreasing the window size by one anytime we loose
sequentiality and increasing in by 1 if we didn't.
With the above set of fixes we got about 28% improvement in DSS workload
which is about 5% more than what we got with the suparna's aio patch.
This patch compared equivalent to suparna's aio patch with aio-stress
run.
It fared better than aio patch for large random io.
We are yet to run a bunch of other benchmarks to evaluate this patch.
We would like to get your inputs on this patch and any suggestions you
may have to improve it. I have enclosed a patch with all these changes
along with some changes to the comments that reflect the new behaviour.
NOTE: the above patch reverts suparna's aio patch.
Andrew Morton [Tue, 30 Dec 2003 07:48:44 +0000 (23:48 -0800)]
[PATCH] shrink_slab acounts for seeks incorrectly
wli points out that shrink_slab inverts the sense of shrinker->seeks: those
caches which require more seeks to reestablish an object are shrunk harder.
That's wrong - they should be shrunk less.
So fix that up, but scaling the result so that the patch is actually a no-op
at this time, because all caches use DEFAULT_SEEKS (2).
Andrew Morton [Tue, 30 Dec 2003 07:48:27 +0000 (23:48 -0800)]
[PATCH] fix pci_update_resource() / IORESOURCE_UNSET on PPC
From: Harald Welte <laforge@gnumonks.org>
[disclaimer: This was posted on the linuxppc list before, BenH asked me=20
to re-post it to lkml]
The prism54 (http://prism54.org) driver for my cardbus adapter works
with 2.4.x, but not 2.6.x on a Titanium G4 Powerbook IV.
On 2.6.x the error message was
PCI:0001:02:00.0 Resource 0 [00000000-00001fff] is unassigned
After investigating differences in the PCI code of 2.4.x and 2.6.x, i
noticed that 2.4.x/arc/ppc/kernel/pci.c:pcibios_update_resource()
contained a couple of lines that unset the IORESOURCE_UNSET bitflag.
In 2.6.x, this is handled by the generic PCI core in
drivers/pci/setup-res.c:pci_update_resource() code. However, the code
is missing the 'res->flags &=3D ~IORESOURCE_UNSET' part.
The below fix re-adds that section from 2.4.x.=20
I'm not sure wether this belongs into the arch-independent PCI api.
Anyway, on PPC it seems to be needed for certain cardbus devices.
Andrew Morton [Tue, 30 Dec 2003 07:48:19 +0000 (23:48 -0800)]
[PATCH] (workaround): avoid raid1 crash during resync with qlogic controllers
qlogic's 16k maximum I/O size bites again. Neil says:
The problems we fixed were all to do with normal IO. This one is resync
IO.
The problem here is that raid1 always does resync in RESYNC_BLOCK_SIZE
(=64k) IOs and if the device doesn't cope - tough.
The simple fix is to #define RESYNC_BLOCK_SIZE to PAGE_SIZE in md/raid1.c
The better fix is to rewrite the raid1 resync code to use bio_add_page.
This means we have to build the read request and the write requests at the
same time, and then when a bio_add_page fails, we back-out the last page
from the bios that have one too many, and then do the read followed by the
writes.
I have some code the nearly does this, but I haven't got it actually
working yet and I am on leave until mid January.
Andrew Morton [Tue, 30 Dec 2003 07:48:11 +0000 (23:48 -0800)]
[PATCH] Remove iso9660 check for sbsector < 660Mb
From: Jon Burgess <mplayer@jburgess.uklinux.net>
The iso9660 filesystem code checks that the "sbsector" option is
positioned within the first 660Mb of the disk.
Today the iso9660 filesystem is used on DVD's which are much bigger than
660Mb and this check prevents the sbsector option being used to specify
the location of the superblock of multisession DVD's.
With this check removed I can mount the second session on a DVD-R by
specifying the sbsector, even though the firmware on that drive returns
bogus data for the TOC.
If an invalid large sector number is entered then a "request beyond end
of device" error is reported elsewhere in the block code, but appears to
do no damage.
Andrew Morton [Tue, 30 Dec 2003 07:47:37 +0000 (23:47 -0800)]
[PATCH] hugepage pagetable freeing fix
From: "Seth, Rohit" <rohit.seth@intel.com>
We recently covered a bug in mm/mmap.c on IA-64. While unmapping a address
space, unmap_region calls free_pgtables to possibly free the pages that are
used for page tables. Currently no distinction is made between freeing a
region that is mapped by normal pages vs the pages that are mapped by
hugepages. Architecture specific code needs to handle cases where PTEs
corresponding to a region that is mapped by hugepages is properly getting
unmapped. Attached please find a patch that makes the required changes in
generic part of kernel. We will need to send a separate IA-64 patch to use
this new semantics. Currently, so not to disturb the PPC (as that is the
only arch that had ARCH_HAS_HUGEPAGE_ONLY_RANGE defined) we are mapping back
the definition of new function hugetlb_free_pgtables to free_pgtables.
"Incorrect number of segments after building list" message.
The macro __BVEC_START assumes a bi_idx of zero when the dm code can
submit a bio with a non-zero bi_idx.
The code has been tested on an 8 way / 8gb OSDL STP machine with a 197G
lvm volume running dbt2 test.
Andrew Morton [Tue, 30 Dec 2003 07:46:56 +0000 (23:46 -0800)]
[PATCH] change two annoying messages from framebuffer drivers
From: Michael Hunold <hunold@convergence.de>
the Linux-on-a-CD system Knoppix has nearly all framebuffer drivers for
2.4.23 compiled in. Additionally, it surpresses most kernel messages by
lowering the kernel log level.
Two framebuffer drivers (clgenfb.c and hgafb.c), however, use KERN_ERR
to say that their particular card has *not* been found which is very
annoying.
Especially the clgenfb.c driver simply says on bootup:
> Couldn't find PCI device
which can really confuse newbie users.
I've already send a patch that fixes this for 2.4 -- Marcelo and Geert
Uytterhoeven have already ack'ed it.
The same change should be done for 2.6, too IMHO.
The appended patch replaces two KERN_ERR with KERN_INFO and additionally
makes the cirrusfb.c message more descriptive.
Andrew Morton [Tue, 30 Dec 2003 07:46:31 +0000 (23:46 -0800)]
[PATCH] Fix memleak on execve failure
From: IWAMOTO Toshihiro <iwamoto@valinux.co.jp>
I found linux-2.6.0-test11 leaks memory when execve fails. I've also
checked the bitkeeper tree and the problem seems to be unchanged.
The attached patch is a partial backout of bitkeeper rev. 1.87 of
fs/exec.c. I guess the original change was a simple mistake.
(free_arg_pages() is a NOP when CONFIG_MMU is defined).
Andrew Morton [Tue, 30 Dec 2003 07:46:23 +0000 (23:46 -0800)]
[PATCH] lib/inflate.c fix
From: "H. Peter Anvin" <hpa@zytor.com>
This patch fixes the "non-terminating inflate" problem that Russell King
complained about on LKML earlier today.
I chose to use "goto" much like zlib does, in order to not require
setjmp/longjmp inside the kernel. It's a bit ugly, but it also lets each
function chose how it needs to be terminated on error, which is a good
thing.
- uses just printk() instead of unneeded fat_fs_panic()
- removes the debug printk
- less verbose on error path
- uses correct a error number on error path
Andrew Morton [Tue, 30 Dec 2003 07:45:07 +0000 (23:45 -0800)]
[PATCH] FAT: Fix the tailing dots on the utf8 path (2/10)
From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Michal Rokos <m.rokos@sh.cvut.cz>
The problem is: even if vfat_striptail_len() counts len of name without
trailing dots and sets len to the correct value, utf8_mbstowcs() doesn't
care about len and takes whole name. So dirs and files with dots can be
created on vfat fs.
Andrew Morton [Tue, 30 Dec 2003 07:44:33 +0000 (23:44 -0800)]
[PATCH] Put fixmaps into /proc/pid/maps via a pseudo-vma
From: David Mosberger <davidm@napali.hpl.hp.com>
This patch makes /proc/PID/maps report the range from FIXADDR_USER_START to
FIXADDR_USER_END as a final pseudo-vma. This is consistent with the notion
that reading /proc/PID/maps tells you about every page containing data that
the process can in fact access, and with things such as ptrace allowing
access to this memory. Without this, userland tools that want to look at all
of a process's accessible pages need special-case knowledge about things such
as the vsyscall DSO page. With this change, existing code that iterates over
the /proc/PID/maps lines will cover those pages like any other. For example,
this lets gdb's "gcore" command synthesize a core file from a live process
that contains the vsyscall DSO page as a real core dump would, using its
existing generic iterator code and no new special cases.
Andrew Morton [Tue, 30 Dec 2003 07:44:09 +0000 (23:44 -0800)]
[PATCH] Fix via686a/KX133 TSC failure
From: Chris Bajumpaa <cbajumpa@or8.net>
This patch fixes a problem with the TSC failing on via686a/KX133
motherboards either reverting to using the pit or deadlocking the machine
alltogether under heavy load. (Specifically Abit KA7/KA7-100).
Message from the log:
Dec 18 18:20:37 grinder kernel: Losing too many ticks!
Dec 18 18:20:37 grinder kernel: TSC cannot be used as a timesource. (Are
you running with SpeedStep?)
Dec 18 18:20:37 grinder kernel: Falling back to a sane timesource.
The snippet of code that was missing from timer_tsc.c comes from
timer_pit.c.
Andrew Morton [Tue, 30 Dec 2003 07:44:00 +0000 (23:44 -0800)]
[PATCH] make gconfig warning removal
From: "Maciej Soltysiak" <solt@dns.toxicfilms.tv>
make gconfig causes this:
scripts/kconfig/gconf.c: In function `on_treeview1_button_press_event':
scripts/kconfig/gconf.c:1175: warning: passing arg 1 of
`gtk_widget_grab_focus' from incompatible pointer type
The fatfs was ignoring the I/O error on two points. If I/O error
happen while checking a free block entries, this checks the all
entries, and reports an I/O error on each entry.
This problem became cause of the disk full by syslogd.
Andrew Morton [Tue, 30 Dec 2003 07:43:36 +0000 (23:43 -0800)]
[PATCH] Fix Summit EBDA parsing
From: Matthew Dobson <colpatch@us.ibm.com>
The code to parse the EBDA (Extended BIOS Data Area) for Summit boxen is
broken because it does not handle Lookout boxen (external boxes full of
additional PCI slots). This patch cleans up some ugliness in
arch/i386/kernel/summit.c as well as fixing the code to handle Lookout boxen
and various other configurations of PCI buses. Without this, Summit PCI bus
to node mappings are totally hosed with Lookout boxen attatched. This patch
depends upon the GENERICARCH fix.
Andrew Morton [Tue, 30 Dec 2003 07:43:28 +0000 (23:43 -0800)]
[PATCH] Fix X86_GENERICARCH & NUMA compile error
From: Matthew Dobson <colpatch@us.ibm.com>
Trying to build a kernel with both CONFIG_X86_GENERICARCH and
CONFIG_NUMA on results in a compile error. This patch fixes that build
problem by adding a config option for NUMA on Summit which is used to
correctly conditionally compile arch/i386/kernel/summit.c and properly
ifdef the function calls used in generic code. Please apply.
Running make -j24 bzImage
arch/i386/mach-generic/built-in.o: In function `mps_oem_check':
arch/i386/mach-generic/built-in.o(.text+0x3ce): undefined reference to
`setup_summit'
arch/i386/mach-generic/built-in.o: In function `acpi_madt_oem_check':
arch/i386/mach-generic/built-in.o(.text+0x468): undefined reference to
`setup_summit'
make: *** [.tmp_vmlinux1] Error 1
Andrew Morton [Tue, 30 Dec 2003 07:43:19 +0000 (23:43 -0800)]
[PATCH] isdn/eicon/eicon_mod.c build fix
From: Adrian Bunk <bunk@fs.tum.de>
CC [M] drivers/isdn/eicon/eicon_mod.o
drivers/isdn/eicon/eicon_mod.c: In function `eicon_exit':
drivers/isdn/eicon/eicon_mod.c:1362: warning: implicit declaration of
function `mca_mark_as_unused'
Andrew Morton [Tue, 30 Dec 2003 07:43:11 +0000 (23:43 -0800)]
[PATCH] Add signal state inheritance control to SELinux
From: Stephen Smalley <sds@epoch.ncsc.mil>
This patch against 2.6.0 adds a control to the SELinux module over the
inheritance of signal-related state upon security context transitions in
order to protect the new security context. If the permission is not
granted by the policy for a given pair of contexts, then transitions
between them will clear itimers, flush all pending signals, forcibly
flush signal handlers, and unblock all signals. Roland McGrath provided
input and feedback on the patch.
Please apply, or let James Morris and me know if you'd like this to be
resubmitted later. Thanks.
projects / history.git / log