- 03 Oct, 2004 1 commit
-
-
Colin Leroy authored
Use interruptible sleep rather than uninterruptible. Partially convert it to the kthread API so the kernel thread doesn't get accidentally signalled. Signed-off-by: Colin Leroy <colin@colino.net> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
- 02 Oct, 2004 2 commits
-
-
Linus Torvalds authored
It became obsolete when the termios locking was changed to use a per-tty semaphore.
-
Benjamin Herrenschmidt authored
Some recent G5s have a problem with PCI/HT probing. They crash (machine check) during the probe of some slot numbers, it seems to be related to some functions beeing disabled by the firmware inside the K2 ASIC. This patch limits the config space accesses to devices that are present in the OF device-tree. This fixes the problem and shouldn't "add" any limitation. If you plug a "random" PCI card with no OF driver, the firmware will still build a node for it with the default set of properties created from the config space. Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
- 03 Oct, 2004 2 commits
-
-
Anton Altaparmakov authored
into cantab.net:/home/src/ntfs-2.6
-
Anton Altaparmakov authored
we did not clear ctx->al_entry but it was still set due to changes in ntfs_attr_lookup() and ntfs_external_attr_find() in particular. Signed-off-by: Anton Altaparmakov <aia21@cantab.net>
-
- 02 Oct, 2004 4 commits
-
-
Linus Torvalds authored
A threaded app that posix-locks and closes the same file in two threads concurrently may result in a posix lock that was never visible to the closer, and that thus needs cleanup on the final fput. Handle it together with the regular flocks.
-
Alan Cox authored
This makes the agreed change of termios locking to be semaphore based sleep locking. This is needed for USB in particular as it has to use messaging to issue terminal mode changes. This code passes Torvalds test grades 0, 1 and 2 (it looks ok, it compiles and it booted). It does mean that a driver cannot take an atomic peek at termios data during an interrupt. Nobody seems to be doing this although some of the driver receive paths for line disciplines will eventually want to (n_tty currently doesn't do this locked on the receive path). Since the ldisc is given a chance to copy any essential bits on the ->set_termios path this seems not to be a problem.
-
Linus Torvalds authored
lock must not be held across the driver/ldisc downcalls. Some drivers need to set device state (baudrate etc) and may need to sleep.
-
Alexander Viro authored
Jeff Mahoney notes: "generic_shutdown_super() will happily call the ->put_super fs method, destroying data structures still in use by the iput (->delete_inode) in progress. The unlink path will call the ->unlink fs method, release the path (thus dropping the reference to the vfsmount, and then call iput. Since the vfsmount reference is dropped back to 1, a umount will succeed, causing the superblock to be cleaned up." Arrgh... Here's the trivial fix: do the final "iput()" a bit earlier in the unlink path. Note: all places that go to exit1: or exit: will have NULL inode, so we are not leaking anything here and it is OK do that iput() early; indeed, the goal of that kludge was to postpone the final iput() past the unlocking the parent for the sake of contention if a wunch of bankers is doing parallel unlink() on files in the same directory and normally it would happen on dput() after vfs_unlink())
-
- 01 Oct, 2004 31 commits
-
-
-
Bartlomiej Zolnierkiewicz authored
Patch to provide support for the following two boards: - Simtec BAST (EB2410ITX) - Thorcom VR1000 Signed-off-by: Ben Dooks <ben@simtec.co.uk> Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
-
Bartlomiej Zolnierkiewicz authored
From: Carsten Haustein <chaus@cs.uni-potsdam.de> A bug in function piix_config_drive_xfer_rate() allows a call of hwif->ide_dma_on(drive) without prior call of piix_config_drive_for_dma(). This results in harddisk configured for UDMA (default?) whereas the highest DMA mode supported by PIIX3 is MWORD2. This bug is supposed to be present in any 2.6.x kernel release and any 2.4.x kernel release since 2.4.21. bart: this should also fix the same bug for PIIXa and PIIXb Fixes bugzilla bug #3473. Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
-
Bartlomiej Zolnierkiewicz authored
Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
-
Bartlomiej Zolnierkiewicz authored
ide-default driver was added long time ago. Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
-
Bartlomiej Zolnierkiewicz authored
- CONFIG_IDE_TASK_IOCTL_DEBUG cannot be defined - function declarations are used instead of calls Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
-
Bartlomiej Zolnierkiewicz authored
Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
-
Bartlomiej Zolnierkiewicz authored
Fixes OOPS on two single channel controllers. Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
-
Chris Wright authored
In sys_mlockall(), flags validation and can_do_mlock() check don't require holding mmap_sem. Move down_write() down a bit, and adjust appropriately. Signed-off-by: Chris Wright <chrisw@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Chris Wright authored
Move the simple can_do_mlock() check before the full rlimits based restriction checks for mlock() and mlockall(). As it is, the check adds nothing. This has a side-effect of eliminating an unnecessary call to can_do_mlock() on the munlockall() path. Signed-off-by: Chris Wright <chrisw@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Chris Wright authored
Only check memlock rlimit against mm->total_vm when mlockall() flags include MCL_CURRENT. Signed-off-by: Chris Wright <chrisw@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Chris Wright authored
Calling mlockall(MCL_FUTURE) will erroneously unlock any currently locked mappings. Fix this up, and while we're at it, remove the essentially unused error variable. Signed-off-by: Chris Wright <chrisw@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
bk://ppc.bkbits.net/for-linus-ppcLinus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
bk://kernel.bkbits.net/davem/sparc-2.6Linus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
bk://kernel.bkbits.net/davem/net-2.6Linus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
bk://bk.arm.linux.org.uk/linux-2.6-serialLinus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
Ben Dooks authored
Patch from Ben Dooks Added code to remove the serial ports registered when the module is unloaded. Cleaned up ifdef'd code, and added copyright header Signed-off-by: Ben Dooks
-
bk://bk.arm.linux.org.uk/linux-2.6-rmkLinus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
Ben Dooks authored
Patch from Ben Dooks Fixed bug where wrong bits where being masked in the configuration registers for the GPIO pins Signed-off-by: Ben Dooks
-
Ben Dooks authored
Patch from Ben Dooks Fix IRQ number for USB over-current on Simtec BAST Signed-off-by: Ben Dooks
-
Catalin Marinas authored
Patch from Catalin Marinas On ARM926EJ-S, the "always assume write" for Jazelle data aborts causes Java code exit with segmentation fault every time it tries to access a read-only page. This patch puts some restrictions on what can be done in the Jazelle state but it allows it to run. Signed-off-by: Catalin Marinas
-
bk://bk.arm.linux.org.uk/linux-2.6-pcmciaLinus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
Russell King authored
From: <janitor@sternwelten.at> Remove unnecessary cs_to_timeout() macro. Use msleep() instead of schedule_timeout() to guarantee the task delays for the desired time. Signed-off-by: Nishanth Aravamudan <nacc@us.ibm.com> Signed-off-by: Maximilian Attems <janitor@sternwelten.at> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Russell King <rmk@arm.linux.org.uk>
-
Harald Welte authored
Fix NAT helper code to update TCP window tracking information if it resizes payload (and thus alrers sequence numbers). This patchlet was somehow lost during 2.4.x->2.6.x port of TCP window tracking :( Signed-off-by: Harald Welte <laforge@netfilter.org> Signed-off-by: David S. Miller <davem@davemloft.net>
-
Alexander Stohr authored
Signed-off-by: David S. Miller <davem@davemloft.net>
-
Yasuyuki Kozakai authored
Signed-off-by: Yasuyuki KOZAKAI <yasuyuki.kozakai@toshiba.co.jp> Signed-off-by: David S. Miller <davem@davemloft.net>
-
Hideaki Yoshifuji authored
Signed-off-by: Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org> Signed-off-by: David S. Miller <davem@davemloft.net>
-
Tom Rini authored
into kernel.crashing.org:/home/trini/work/kernel/pristine/for-linus-ppc
-
David S. Miller authored
Signed-off-by: David S. Miller <davem@davemloft.net>
-
http://lia64.bkbits.net/linux-ia64-release-2.6.9Linus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
David Gibson authored
We recently changed the VSID allocation on PPC64 to use a new scheme based on a multiplicative hash. It turns out our choice of multiplier (the largest 28-bit prime) wasn't so great: with large contiguous mappings, we can get very poor hash scattering. In particular earlier machines (without 16M pages) which had a reasonable about of RAM (>2G or so) wouldn't boot, because the linear mapping overflowed some hash buckets. This patch changes the multiplier to something which seems to work better (it is, rather arbitrarily, the median of the primes between 2^27 and 2^28). Some more theory should almost certainly go into the choice of this constant, to avoid more pathological cases. But for now, this choice fixes a serious bug, and seems to do at least as well at scattering as the old choice on a handful of simple testcases. Signed-off-by: David Gibson <david@gibson.dropbear.id.au> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-