- 12 Jan, 2005 11 commits
-
-
David Woodhouse authored
In ChangeSet 1.2370, 2005/01/11 17:41:32-08:00, tglx@linutronix.de wrote: > > [PATCH] ppc: remove duplicate define > > The MMCR0_PMXE is already defined in reg.h... Er, no it's not. But perhaps it should be...
-
Paul Mackerras authored
Ingo presumably didn't notice that ppc64 already had a functional _raw_read_trylock when he added the #define to use the generic version. This just removes the #define so we use the ppc64-specific version again. Signed-off-by:
Paul Mackerras <paulus@samba.org> Signed-off-by:
Linus Torvalds <torvalds@osdl.org>
-
Jens Axboe authored
Currently we only print the default io scheduler if the kernel chooses, not if the user/bootloader has specified one. This patch saves the extra line in dmesg but always notified of the default choice by appending (default) to that line: .. io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) .. Patch originally from Srihari Vijayaraghavan, modified by me. Signed-off-by:
Jens Axboe <axboe@suse.de> Signed-off-by:
-
Jens Axboe authored
The accounting can go bad in the requeue hook, it must check the accounted flag to make sure it was previously considered in the driver. Signed-off-by:
-
Keith Owens authored
Signed-off-by:
Keith Owens <kaos@sgi.com> Signed-off-by:
-
Ivan Kokshaysky authored
This apparently explains some weird IO failures reported in last two months. Only non-bwx (including generic) kernels were affected. Acked-by:
Richard Henderson <rth@twiddle.net> Signed-off-by:
-
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
-
Linus Torvalds authored
This enables it only for debug kernels, and also makes sure that if some external module is still broken, we don't leave the mmap-sem locked after warning about it.
-
Marcelo Tosatti authored
It seems to be general consensus that its safer to require all do_brk() callers to grab mmap_sem, and have do_brk to warn otherwise. This is what the following patch does. Similar version has been changed to in v2.4. Signed-off-by: -
Linus Torvalds authored
We had all the locking right, but we didn't check whether one of the threads now no longer needed to expand, so we could incorrectly _shrink_ the stack in the other thread instead (not only causing segfaults, but since we didn't do a proper unmap, we'd possibly leak pages too). So re-check the need for expand after getting the lock. Noticed by Paul Starzetz.
-
- 11 Jan, 2005 29 commits
-
-
Andi Kleen authored
Fix a long standing bug: numa=off only worked as last argument on the command line. Signed-off-by:
Andi Kleen <ak@suse.de> Signed-off-by:
-
Andi Kleen authored
Signed-off-by:
-
Andi Kleen authored
Fix K8 node discovery after nodemask changes. Signed-off-by:
-
Andi Kleen authored
Fix fallout from the recent nodemask_t changes. The node ids assigned in the SRAT parser were off by one. I added a new first_unset_node() function to nodemask.h to allocate IDs sanely. Signed-off-by:
-
Frederick Li authored
-
Andrew Morton authored
drivers/net/3c515.c: In function `__check_rx_copybreak': drivers/net/3c515.c:406: warning: return discards qualifiers from pointer target type drivers/net/3c515.c: At top level: drivers/net/3c515.c:406: warning: initialization discards qualifiers from pointer target type Signed-off-by:Andrew Morton <akpm@osdl.org>
-
Andrew Morton authored
Signed-off-by: -
Andrew Morton authored
drivers/net/eepro.c:1799: initializer element is not constant drivers/net/eepro.c:1799: (near initialization for `__param_arr_io.num') drivers/net/eepro.c:1800: initializer element is not constant drivers/net/eepro.c:1800: (near initialization for `__param_arr_irq.num') drivers/net/eepro.c:1801: initializer element is not constant drivers/net/eepro.c:1801: (near initialization for `__param_arr_mem.num') Signed-off-by: -
Jeff Garzik authored
into pobox.com:/garz/repo/net-drivers-2.6
-
Linus Torvalds authored
-
Hisashi Hifumi authored
I found bugs on error handlings in the functions arround the ext3 file system, which cause inadequate completions of synchronous write I/O operations when disk I/O failures occur. Both 2.4 and 2.6 have this problem. I carried out following experiment: 1. Mount a ext3 file system on a SCSI disk with ordered mode. 2. Open a file on the file system with O_SYNC|O_RDWR|O_TRUNC|O_CREAT flag. 3. Write 512 bytes data to the file by calling write() every 5 seconds, and examine return values from the syscall. from write(). 4. Disconnect the SCSI cable, and examine messages from the kernel. After the SCSI cable is disconnected, write() must fail. But the result was different: write() succeeded for a while even though messages of the kernel notified SCSI I/O error. By applying following modifications, the above problem was solved. Signed-off-by:Hisashi Hifumi <hifumi.hisashi@lab.ntt.co.jp> Signed-off-by:
-
Ingo Molnar authored
Make PREEMPT_BKL depend on PREEMPT alone - doesnt make sense to enable it on SMP && !PREEMPT kernels. (other than testing.) Signed-off-by:
Ingo Molnar <mingo@elte.hu> Signed-off-by:
-
Dominik Brodowski authored
From: Manfred Spraul One bios assigns a small window for i/o access to yenta bridges. But there are Cardbus cards that needs lots of i/o ports. yenta usually honors the bios selected values, except if the bios choice is clearly invalid. The patch allows an override from the command line. Signed-Off-By:
Manfred Spraul <manfred@colorfullife.com> Signed-Off-By:
Dominik Brodowski <linux@brodo.de> Signed-off-by:
-
Dominik Brodowski authored
Also lock the ->exit() function in rsrc_nostatic Signed-off-by:
-
Dominik Brodowski authored
Remove the typedef'ing of struct resource_map. Signed-off-by:
-
Dominik Brodowski authored
Move the resource databases and the "mem_probe" flag into a struct specific to rsrc_nonstatic, as it is not needed for the SS_CAP_STATIC_MAP case. Saves a few bytes, and makes code clearer (in my opinion) Signed-off-by:
-
Dominik Brodowski authored
Make rsrc_nonstatic an independent module. Signed-off-by:
-
Dominik Brodowski authored
Move all the "nonstatic" code to a new file, and link it into pcmcia_core.ko Signed-off-by:
-
Dominik Brodowski authored
re-direct calls to adjust_resource_info for MEM and IO. Signed-off-by:
-
Dominik Brodowski authored
Calls to adjust_mem_region only happen if !SS_CAP_STATIC_MAP. Signed-off-by:
-
Dominik Brodowski authored
Calls to find_io_region only happen if !SS_CAP_STATIC_MAP. Signed-off-by:
-
Dominik Brodowski authored
Calls to adjust_io_region only happen if !SS_CAP_STATIC_MAP. Signed-off-by:
-
Dominik Brodowski authored
validate_mem() does only make sense for !SS_CAP_STATIC_MAP sockets. Therefore, re-direct validate_mem() calls only for those. The newly added redirection layer will allow for a "library" module named "rsrc_nonstatic" which contains the resource database handling code, and it will only need to be loaded for the drivers which need it. Signed-off-by:
-
Dominik Brodowski authored
Make the io and mem db per-socket, as different sockets may have different requirements or may not even need the resource db at all (SS_CAP_STATIC_MAP). Updated to make rsrc_mem_probe per-socket and to remove unnecessary and even broken check for empty list as per Russell King's suggestions. Signed-off-by:
-
Dominik Brodowski authored
Instead of "memory_cs", BIND_MTD, {FIRST,NEXT}_REGION, 2.6. kernels use the "pcmciamtd" driver which doesn't need these functions. Cardmgr still calls it in default configuration, so warn the user about changes necessary to /etc/pcmcia/config , and remove the now unused code. Signed-off-by: -
Dominik Brodowski authored
Remove the dev_info - contained name from struct client_t Signed-off-by:
-
Dominik Brodowski authored
Remove the no longer used "name" parameter from alloc_io_space, find_{io,mem}_region. Signed-off-by: -
Dominik Brodowski authored
Remove the "Attributes" entry of struct client_t -- _all_ in-kernel drivers did set it to INFO_IO_CLIENT | INFO_CARD_SHARE anyway, and the pcmcia core didn't care at all what this value was set to. Also, remove the setting of the respective request field in all in-kernel drivers -- the request structure is kept the same, though, to keep external drivers compiling. Signed-off-by:
-
Dominik Brodowski authored
PendingEvents is unused, so remove it Signed-off-by:
-
