- 14 Aug, 2003 28 commits
-
-
Jeroen Vreeken authored
-
Jeroen Vreeken authored
-
Randy Dunlap authored
-
David S. Miller authored
into nuts.ninka.net:/home/davem/src/BK/net-2.5
-
Linus Torvalds authored
This fixes the DMA interface to be backwards compatible with older XFree86 versions, by looking at the I810_INIT_DMA parameters and figuring out old version semantics.
-
Linus Torvalds authored
-
Linus Torvalds authored
CLONE_THREAD without CLONE_DETACHED will now return -EINVAL, and for a while we will warn about anything that uses it (there are no known users, but this will help pinpoint any problems if somebody used to care about the invalid combination).
-
Christophe Saout authored
A part of the 64 bit kdev_t patch already got merged, and it changes the format of /sys/block/<dev>/dev from %02x%02x to %u:%u. The partition could must also be changed. e.g. cat /sys/block/hda/hda5/dev should return 3:5 instead of 0305
-
Fruhwirth Clemens authored
It was caused by improper IV calculation in loop.c
-
Fruhwirth Clemens authored
cryptoloop won't oops anymore if ECB mode is requested.
-
Andi Kleen authored
Just call them from the x86-64 entry code. Also implement the x86-64 specific sys32_timer_create.
-
Andi Kleen authored
Add 32bit->64bit conversion functions for POSIX timers. I kept timer_create architecture specific, because it does signal specific stuff which is not portable enough for generic compat.
-
Andi Kleen authored
Add compat_sys_utimes for 32bit->64bit utimes conversion
-
Andi Kleen authored
Add compat_* functions for statfs64. The 32bit layout unfortunately does not match x86-64.
-
Russell King authored
This patch allows modules to work for ARM, and is the one thing which prevents the standard tree from building for any ARM machine. After reviewing the /proc/kcore and kclist issues, I've decided that I'm no longer prepared to even _think_ about supporting /proc/kcore on ARM - it just gets too ugly, and adds too much code to make it worth the effort, the time or the energy to implement a solution to that problem. /proc/kcore should probably go away, but in the meantime this just allows ARM to ignore the issues.
-
Bartlomiej Zolnierkiewicz authored
makes 2.4->2.6 diff noticeable smaller
-
Bartlomiej Zolnierkiewicz authored
and add stripped down buffer_head variant (struct idetape_bh). ide-tape is accessed by a char device (not a block one!), it uses block layer only to queue requests.
-
Bartlomiej Zolnierkiewicz authored
also add missing Kconfig help entry from 2.4.x
-
Bartlomiej Zolnierkiewicz authored
- more locking fixes - preserve gendev.parent of the old hwif in the new one
-
Bartlomiej Zolnierkiewicz authored
Noticed by Andries.Brouwer@cwi.nl. Also: - kill probe_lba_addressing() wrapper - rename hwif->addressing to hwif->no_lba48
-
Bartlomiej Zolnierkiewicz authored
From Andries.Brouwer@cwi.nl. - always use drive->capacity48 and kill drive->capacity I've changed drive->capacity48 to drive->capacity64 to avoid confusion.
-
Bartlomiej Zolnierkiewicz authored
From Andries.Brouwer@cwi.nl. - kill redundant, never executed code in lba_capacity_is_ok() - add idedisk_supports_{hpa,lba48}() helpers - don't recalculate drive->cyl for drives using LBA addressing, we never fall-back to CHS, so its useless and confusing - remove wrong drive->head and drive->sect assignments for LBA-48 - don't overwrite id->lba_capacity and id->lba_capacity_2
-
Bartlomiej Zolnierkiewicz authored
HDIO_GETGEO_BIG_RAW is an ide specific hack introduced in 2.3.99-pre3. There are no known programs using this ioctl. Its aim was to provide current CHS translation to the user-space, but very often it provides what driver thinks is a current translation (drive with LBA have to support only one physical translation, also drive may not support chosen translation and there is no return value check). hdparm -I can be used instead, it provides correct information (and bogus data is still accessible through /proc/ide/hdX/geometry).
-
bk://kernel.bkbits.net/lord/xfs-2.5Linus Torvalds authored
into home.osdl.org:/home/torvalds/v2.5/linux
-
ssh://lord@kernel.bkbits.net/xfs-2.5Stephen Lord authored
into jen.americas.sgi.com:/src/lord/bitkeeper/xfs-2.5
-
Nathan Scott authored
by moving blk queue manipulation down into pagebuf. Fix some busted comments in page_buf.h, use a more descriptive name for __pagebuf_iorequest. SGI Modid: 2.5.x-xfs:slinx:155788a
-
Michael Plump authored
The help for CONFIG_DEVPTS_FS claims that devfs "is a more general facility". But that apparently hasn't been true since 2.5.68. This patch removes that claim, and adds a warning to the DEVFS_FS help.
-
http://linux-acpi.bkbits.net/linux-acpiLinus Torvalds authored
into home.osdl.org:/home/torvalds/v2.5/linux
-
- 13 Aug, 2003 12 commits
-
-
Stephen Lord authored
into kernel.bkbits.net:/home/lord/xfs-2.5
-
Alexander Viro authored
From A1tmblwd@netscape.net
-
Kai Mäkisara authored
This updates my email address.
-
Kai Mäkisara authored
This corrects the following problem: - release user buffer mapping early in read path (prevent oops in some HBA drivers)
-
John Levon authored
Patch by Ivan Gyurdiev.
-
Corey Minyard authored
Here are some minor updates to the IPMI driver. They fix the following: * A missing check for copy_to_user() in the watchdog driver. * Removal of unnecessary check_region() calls. * Fixes for the ACPI configuration. The previous one would only work with memory addresses, this will work with memory addresses, ports, and hadle checking that the type is correct.
-
Andries E. Brouwer authored
The HPT366 code is broken - it tries to set the interface to too high a speed, which leads to error messages at boot time and/or to data corruption. The typical effect at boot time is hde: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error } hde: set_drive_speed_status: error=0x04 { DriveStatusError } Fixed thus.
-
Neil Brown authored
When a socket has a request ready it notifies a server thread. When the thread has 'received' the request it calls svc_sock_received to confirm the fact. In some cases, svc_sock_received would be called an extra time and this could lead to linked-list corruption and bad problems.
-
Neil Brown authored
raid5 tries to honour RWA_MASK, but messes it up and can return bad data. Just ignore RAW_MASK for now.
-
Andi Kleen authored
Without these changes an x86-64 NUMA kernel won't boot in many configurations. The main change is the improved IOMMU code which supports merging of mappings and has various bugfixes. - Update defconfig - Use argument ptregs in 32bit elf_core_copy_task_fpregs - Harden aperture fixup code: read aperture from the AGP bridge if needed, better error checking. - Support nmi_watchdog=panic to panic on watchdog trigger - IOMMU: Support panic on IOMMU overflow (iommu=panic) - IOMMU: Force SAC for mappings >40bits when iommu=force is active (this can potentially give better performance) - IOMMU: Cache northbridges for faster TLB flush - IOMMU: Fix SMP race in TLB flush - IOMMU: Merge pci_alloc_consistent and pci_map_single - IOMMU: Clean up leak tracing - IOMMU: Rewrite pci_map_sg, support merging of mappings On overflow fall back to piece-by-piece mapping. - IOMMU: Tell block layer to assume merging when iommu force is active (this gives better performance with MTP fusion, drawback is that the overflow/fragmentation handling of the IOMMU area is still a big dubious with that) - Fix/clean up per cpu data - Add 64bit clean time(2) - Export cpu_callout_map for IPv6 - Handle nodes with no own memory in NUMA discovery. This fixes boot on various newer Opteron motherboards where the memory is only connected to a single CPU. - Fix fallback path for failed NUMA discovery. numnodes has to be reset. - Check for enabled nodes in NUMA discovery (Eric Biederman) - Remove NUMA emunodes support. Has badly bitrotted. - Add __clear_bit_string for IOMMU code - Add new 32bit system calls to ia32_unistd.h - Remove duplicate default_do_nmi prototype - Make PCI_DMA_BUS_IS_PHYS dependent on no_iommu - Fix padding length of siginfo_t to match glibc - More pci direct access functions.
-
Geert Uytterhoeven authored
-
Muli Ben-Yehuda authored
This patch fixes a kernel lockup with 2.6.0-test2 when the trident.c OSS driver is loaded and the driver attempts to initialize the card. The problem is that in ali_ac97_get() we lock the card->lock spinlock, but never release it on the good path, only on the error path. This patch adds the missing spin_unlock_irqrestore(). This bug snuck in in a 2.4 sync from Alan, and 2.4 appears to suffer from the same problem. A patch for that will be send to Marcelo momentarily.
-