- 13 Dec, 2004 6 commits
-
-
Gerd Knorr authored
ObviouslyCorrect[tm] buildfix ;) Signed-off-by: Gerd Knorr <kraxel@bytesex.org> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Heiko Carstens authored
The patch below fixes an ext2/ext3 memory leak: the *_fill_super functions allocate percpu data structures but don't free them in *_put_super. Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Andrew Morton authored
Use pid_alive() rather than testing for a zero value of ->pid. Is the right thing to do and addresses an oops dereferencing real_parent which one person reported. Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
David Brownell authored
When drives go offline, e.g. usb-storage disconnect, the upper layers don't behave very intelligently yet: ext3 over scsi keeps retrying reads, logging three lines for each error: 10:58:31 scsi0 (0:0): rejecting I/O to dead device 10:58:31 EXT3-fs error (device sda1): ext3_find_entry: reading directory #18089296 offset 0 10:58:31 10:59:47 EXT3-fs error (device sda1): ext3_find_entry: reading directory #18089296 offset 0 This patch shrinks that log spam by the trivial third, getting rid of those needless blank lines. It's not clear to me why the "no such device" errors don't immediately make ext3 (or is it the block layer?) give up ... maybe someone else can make Linux not retry after those errors. Signed-off-by: David Brownell <dbrownell@users.sourceforge.net> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Andrew Morton authored
We need to set the PF_SYNCWRITE when performing direct-io writes. Otherwise the anticipatory scheduler exhibits bad read-starves-write problems. Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Paul Mackerras authored
Recently I tried booting a UP kernel on a 1-processor logical partition on a POWER4 system. It failed because the CPU we happened to be running on was CPU 2, but hard_smp_processor_id() is defined to 0 for !CONFIG_SMP. (Note that this code runs quite early, as part of init_IRQ, so hard_smp_processor_id() should be the physical ID of the boot cpu.) This patch does a minimal fix to make it work. I think this patch should go in 2.6.10. Ultimately I think the hard_smp_processor_id() definition should be removed from include/linux/smp.h, but that carries a risk of breaking other architectures and probably shouldn't be done pre 2.6.10. Signed-off-by: Paul Mackerras <paulus@samba.org> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
- 12 Dec, 2004 9 commits
-
-
Jens Axboe authored
Found a subtle bug that caused mount errors on a SATA drive with barriers on reiser and ext3, where it should have recovered and just turned off barriers. The problem is that the EOPNOTSUPP error isn't being propagated properly to the bounced bio. This patch fixes that by correctly passing error all the way down. Signed-off-by: Jens Axboe <axboe@suse.de> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Paul Mackerras authored
This patch is from Will Schmidt <willschm@us.ibm.com>, with some extra comments from me. On iSeries and on POWER5 machines, there is a data structure which is used for communication between the hypervisor and the kernel, called the `lppaca'. The kernel tells the hypervisor where it is, and the hypervisor requires that it doesn't cross a page boundary. With other changes in the last few months we have ended up with a situation where it could cross a page boundary. This patch increases the alignment requirement for the struct to make sure that it can't cross a page boundary. This is a bug fix and should go into 2.6.10. Signed-off-by: Will Schmidt <willschm@us.ibm.com> Signed-off-by: Paul Mackerras <paulus@samba.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
bk://cifs.bkbits.net/linux-2.5cifsLinus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
Steve French authored
allowing buffer size to be changed Signed-off-by: Steve French (sfrench@us.ibm.com)
-
-
-
Adrian Bunk authored
The patch below by "Petri T. Koistinen" <petri.koistinen@iki.fi> in Rusty's trivial patches is IMHO a candidate for 2.6.10 . Signed-off-by: Adrian Bunk <bunk@stusta.de> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
-
Linus Torvalds authored
It contains the thread info pointer. That's not something that user mode can really use for anything interesting, but it's also not something that user mode should ever really see. Pointed out by Brad Spender as being in PaX.
-
- 11 Dec, 2004 3 commits
-
-
Steve French authored
Signed-off-by: Steve French (sfrench@us.ibm.com)
-
Steve French authored
Signed-off-by: Steve French (sfrench@us.ibm.com)
-
Steve French authored
buffers and for maximum number of simultaneous requests. Fix directio of userbuffers to use copy_to_user. Signed-off-by: Steve French (sfrench@us.ibm.com)
-
- 10 Dec, 2004 14 commits
-
-
-
Bartlomiej Zolnierkiewicz authored
Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
-
Bartlomiej Zolnierkiewicz authored
Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
-
Bartlomiej Zolnierkiewicz authored
From: Edward Falk <efalk@google.com> Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
-
Bartlomiej Zolnierkiewicz authored
From: Alan Cox <alan@lxorguk.ukuu.org.uk> When we issue an ide command the status bits don't become valid for 400nS. In the DMA case ide_execute_command handles this but in the PIO case we don't do the needed locking, use OUTBSYNC to avoid posting or delay. This means that in some situations we can execute the command handler in PIO mode before the command status bits are valid and the handler may read and act wrongly. Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
-
Bartlomiej Zolnierkiewicz authored
From: Clear Zhang <Clear.Zhang@uli.com.tw> Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
-
Bartlomiej Zolnierkiewicz authored
From: Pascal Lengard <lklm@lengard.net> Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
-
Bartlomiej Zolnierkiewicz authored
pdc202xx_old_cable_detect() always returns '0' (which means 80c cable) due to a sloppy coding - result of CIS & mask is truncated to 8 bits although CIS holds cable info in bits 10-11. Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
-
Bartlomiej Zolnierkiewicz authored
Reported to work OK by Alexander E. Patrakov <patrakov@ums.usu.ru>. Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
-
Bartlomiej Zolnierkiewicz authored
Reported to work OK by Junio C Hamano <junkio@cox.net>, DervishD <lkml@dervishd.net> and Anton <_xman_@mail.ru>. Fixes bugzilla bug #3730. Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
-
Steve French authored
[CIFS] Allow peek to return less than smb header so we do not prematurely kill session to server when socket stack is busy. Signed-off-by: Steve French (sfrench@us.ibm.com)
-
Steve French authored
Signed-off-by: Steve French (sfrench@us.ibm.com)
-
Linus Torvalds authored
It's a purely theoretical bug, since the kmalloc() failure that might "leak" file descriptors cannot actually happen (we do not ever fail small GFP_KERNEL allocations), but it's good to do things properly. Noted by Brad Spender.
-
Linus Torvalds authored
Noted by Georgi Guninski
-
- 09 Dec, 2004 8 commits
-
-
-
Steve French authored
dnotify to be disabled by default. Fix dnotify endianness. Signed-off-by: Steve French (sfrench@us.ibm.com)
-
bk://linux-scsi.bkbits.net/scsi-for-linus-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
-
Greg Kroah-Hartman authored
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>
-
Nishanth Aravamudan authored
Description: Bug 387 (http://bugzilla.kernel.org/show_bug.cgi?id=387) is fixed by the attached patch, which sends waitqueue wake-ups to all the appropriate wait-queue entries when a device is removed from the system. Signed-off-by: Nishanth Aravamudan <nacc@us.ibm.com> Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>
-
Greg Kroah-Hartman authored
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>
-
Greg Kroah-Hartman authored
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>
-