- 23 Aug, 2004 40 commits
-
-
Andrew Morton authored
drivers/net/Kconfig:1749:warning: 'select' used by config symbol 'VIA_VELOCITY' We renamed CONFIG_CRC16. Signed-off-by:
Andrew Morton <akpm@osdl.org> Signed-off-by:
Linus Torvalds <torvalds@osdl.org>
-
Andrey Panin authored
Signed-off-by:
Andrey Panin <pazke@donpac.ru> Signed-off-by:
-
Adrian Bunk authored
cciss uses /proc to hook into the SCSI subsystem. If you do not build /proc support into your kernel then you should also disable tape support in the driver. Signed-off-by:
Adrian Bunk <bunk@fs.tum.de> Signed-off-by:
-
Mike Miller authored
This patch updates the maintainers list for HP drivers. Signed-off-by:
-
Mike Miller authored
This patch changes our read_ahead to 1024. This has been shown to increase performance. Signed-off-by:
-
Mike Miller authored
This patch fixes our usage of pdev->intr. We were truncating it to an unchar. We were also reading it before calling pci_enable_device. This patch fixes both of those. Thanks to Bjorn Helgaas for the patch. Signed-off-by:
-
Mike Miller authored
Somehow I managed to get the wrong PCI ID in pci_ids.h. 3210 is the correct PCI ID, 3211 is the subsystem ID. Signed-off-by:
-
Mike Miller authored
This patch fixes the vendor ID for our cciss based SATA controller due out later this year and adds the new PCI ID to pci_ids.h. Also changes DRIVER_NAME to HP CCISS. Signed-off-by:
-
Mike Miller authored
This patch fixes our cylinder calculations. Without his fix the number of cylinders maxes out at 65535. Signed-off-by:
-
Mike Miller authored
This patch fixes our output in /proc to display the logical volume sizes and RAID levels correctly. Without this patch RAID level will always be 0 and size may be displayed as 0GB. Signed-off-by:
-
Mike Miller authored
This patch addresses a problem with our utilities. We must zero out the buffer before copying their data into it to prevent bogus info when switching between SCSI & SATA or SAS drives. Signed-off-by:
-
Mike Miller authored
This patch fixes our usage of copy_to_user. We were passing in the size of the address rather than the size of the struct. Signed-off-by:
-
Anton Blanchard authored
Fix another gcc 3.5 compile issue, this time the default_policy prototype was not marked static whereas the definition was. There is no need for the prototype, so remove it. Signed-off-by:
Anton Blanchard <anton@samba.org> Signed-off-by:
-
Rik van Riel authored
Since various gnupg users have indicated that gpg wants to mlock 32kB of memory, I created the patch below that increases the default mlock ulimit to 32kB. This is no security problem because it's trivial for processes to lock way more memory than this in page tables, network buffers, etc. In fact, since this patch allows gnupg to mlock to prevent passphrase data from being swapped out, the security people will probably like it ;) This gets the new per-user mlock limit a bit more testing, too. Signed-off-by:
Rik van Riel <riel@redhat.com> Signed-off-by:
-
Rik van Riel authored
Here is the last agreed-on patch that lets normal users mlock pages up to their rlimit. This patch addresses all the issues brought up by Chris and Andrea. From: Chris Wright <chrisw@osdl.org> Couple more nits. The default lockable amount is one page now (first patch is was 0). Why don't we keep it as 0, with the CAP_IPC_LOCK overrides in place? That way nothing is changed from user perspective, and the rest of the policy can be done by userspace as it should. This patch breaks in one scenario. When ulimit == 0, process has CAP_IPC_LOCK, and does SHM_LOCK. The subsequent unlock or destroy will corrupt the locked_shm count. It's also inconsistent in handling user_can_mlock/CAP_IPC_LOCK interaction betwen shm_lock and shm_hugetlb. SHM_HUGETLB can now only be done by the shm_group or CAP_IPC_LOCK. Not any can_do_mlock() user. Double check of can_do_mlock isn't needed in SHM_LOCK path. Interface names user_can_mlock and user_substract_mlock could be better. Incremental update below. Ran some simple sanity tests on this plus my patch below and didn't find any problems. * Make default RLIM_MEMLOCK limit 0. * Move CAP_IPC_LOCK check into user_can_mlock to be consistent and fix but with ulimit == 0 && CAP_IPC_LOCK with SHM_LOCK. * Allow can_do_mlock() user to try SHM_HUGETLB setup. * Remove unecessary extra can_do_mlock() test in shmem_lock(). * Rename user_can_mlock to user_shm_lock and user_subtract_mlock to user_shm_unlock. * Use user instead of current->user to fit in 80 cols on SHM_LOCK. Signed-off-by:
-
Ram Pai authored
Here is a consolidated readahead patch that takes care of the performance regression seen with multiple threaded writes to the same file descriptor. The patch does the following: 1. Instead of calculating the average count of sequential access in the read patterns, it calculates the average amount of hits in the current window. 2. This average is used to guide the size of the next current window. 3. Since the field serial_cnt in the ra structure does not make sense with the introduction of the new logic, I have renamed that field as currnt_wnd_hit. This patch will help the read patterns that are not neccessarily sequential but have sufficient locality. However it may regress random workload. Results: 1. Berkley Shands has reported great performance with this patch. 2. iozone showed negligible effect on various read patterns. 3. DSS workload saw neglible change. 4. Sysbench saw a small improvement. Signed-off-by:
-
Ram Pai authored
Ok I have enclosed the results for the recent readahead fixes. The summary is: there is no significant improvement or decrease in performance of (DSS workload, iozone, sysbench) The increase or decrease is in the margin of errors. I have enclosed a patch that partially backs off Miklos's fix. Shane Shrybman correctly pointed out that the real fix is to set ra->average value to max/2 when we move from readahead-off mode to readahead-on mode. The other part of Miklos's fix becomes irrelevent. Signed-off-by:
-
Arjan van de Ven authored
LOOP_CHANGE_FD is an ULONG compatible ioctl, basically same calling convention as LOOP_SET_FD; mark it as such in the compat ioctl list. Signed-off-by:
-
Randy Dunlap authored
'make buildcheck' indicates that these functions should not be in an __exit section, so undo that. Yes, they can be called from .text. Signed-off-by:
Randy Dunlap <rddunlap@osdl.org> Signed-off-by:
-
Zou Nanhai authored
Here is a patch to fix a problem of might-sleep-in-atomic which David Mosberger mentioned at http://www.gelato.unsw.edu.au/linux-ia64/0407/10526.html On IA64 platform, a might-sleep-in-atomic warning raise while dumping a multi-thread process. That is because elf_core_dump holds the tasklist_lock before the kernel does a access_process_vm in elf_core_copy_task_regs, This patch detached elf_core_copy_task_regs function from inside tasklist_lock to remove the warning. Signed-off-by:
-
Thierry Vignaud authored
fix compiling oldconfig with gcc-3.5: Signed-off-by:
-
Iñaky Pérez-González authored
This patch renames fs/aio.c:'struct timeout' to 'struct aio_timeout'. The rationale behind this decision is this type is used only inside the aforementioned aio.c file and being the type name very generic, it is likely to cause namespace conflicts in the future. I actually found it while working on an extended schedule_timeout()- like API used by robust mutexes but usable by anyone. There I declared a 'struct timeout' and aio.c complained about it. I could have also renamed the struct for the schedule_timeout() like API, but being the aio.c one specific to the file, I thought it might make more sense to rename the later. Signed-off-by:
Inaky Perez-Gonzalez <inaky.perez-gonzalez@intel.com> Signed-off-by:
-
Matt Mackall authored
If netpoll attempts to use a device without polling support, it will oops when shutting down. This adds a check that we've actually attached to a device. Signed-off-by:
Matt Mackall <mpm@selenic.com> Signed-off-by:
-
Andrew Morton authored
Remove now-unneeded open-coded unlikelies around IS_ERR(). Signed-off-by:
-
Andrew Morton authored
It seems fair to assume that it is always unlikely that IS_ERR will return true. This patch changes the gcc-3.4-generated kernel text by ~500 bytes (less) so it's fair to assume that the compiler is indeed propagating unlikeliness out of inline functions. Signed-off-by:
-
Badari Pulavarty authored
I found one more accounting inconsistency with dio_pages_in_io. This is a day-one bug and I started hitting it on latest -mm due to the recent changes to dio_pages_in_io calculations to be exact. If the file is badly fragmented (no contiguous blocks at all), and the user buffer is not page aligned - we need to create IO for each disk block with 2 pages. (bio with 2 vecs). dio_bio_add_page() should not decrement dio_pages_in_io for every add page. It should only decrement, it only if its done with that page and moving on to next page. (since dio_pages_in_io represent how many actual pages we are operating on). Here is the patch to fix this accounting. Without this patch, we will hit BUG() in dio_new_bio() with O_DIRECT on filesystems. Signed-off-by:
-
Badari Pulavarty authored
We're being lazy when calculating the size of the needed BIO, allocating two extra pages to cope with funny alignments. Change that to be exact, thus allocating smaller BIOs someties. Signed-off-by:
-
Corey Minyard authored
Some people found some bugs and some missing functions in the IPMI driver, so I have patching things together for the next release. The attached patch moves to version 33 of the driver and contains: * SMBIOS table support for specifying register spacing. This allows non-contiguous registers to be specified and some machines do this. * ACPI table updates to support all the possible register sizes and bit offsets into the registers for the IPMI information. * Support for command line parameters to specify register spacing, sizes, and bit offsets. * Support for power control with IPMI. This allows a halt to power down a machine with IPMI. * A fix for a race condition with interrupts enabled on an SMP machine. A lock was released then reclaimed, but there was code later that assumed that had not happened. * A fix for protecting the driver against bad responses from the controller chip. In the past, the driver had assumed that the controller chip would not give it bad data. This has turned out to be a bad assumption * ACPI interrupt handlers now return a return value, adjust accordingly. Thank you to all the people who helped me with this. Signed-off-by:
Corey Minyard <minyard@acm.org> Signed-off-by:
-
Corey Minyard authored
Makes the IPMI watchdog more consistent with the other watchdog drivers. I have tested this and it seems to work correctly. I also added docs for the interface change. - support disabling watchdog by writing 'V' to device. - unify printk() - use atomic bit operations on ipmi_wdog_open Signed-off-by:
Arkadiusz Miskiewicz <arekm@pld-linux.org> Signed-off-by:
-
Paul Clements authored
Here's a patch to fix a race condition in nbd that was causing struct request corruption (requests were being freed while still in use). This patch improves on the previous one, which admittedly was a bit dodgy, using struct request's ref_count field (I should have listened to Jens in the first place :). This should fix all the corner cases related to struct request usage/freeing in nbd. My stress tests do a lot better with this patch applied. Signed-off-by:
-
William Lee Irwin III authored
Nuke the real undefined symbol in sparc32. This is the only real hit from ldchk on sparc32; the rest are all btfixup-related (Sam Ravnborg and I are working on addressing that). Signed-off-by:
-
Sean Neakums authored
This patch kills two printks from UDF that announce its registration and unregistration. Since one can determine which filesystems are present by examining /proc/filesystems, these messages strike me as noise. Signed-off-by:
Sean Neakums <sneakums@zork.net> Signed-off-by:
-
Janice M. Girouard authored
Signed-off-by:
-
Jens Axboe authored
A few fixes related to cdrom media event notification. These are from Alexander Kern <alex.kern@gmx.de> Signed-off-by:
Jens Axboe <axboe@suse.de> Signed-off-by:
-
Neil Brown authored
Fix a problem wherein device nodes on a ro-exported mount cannot be opened read/write. Signed-off-by:
-
Neil Brown authored
To purge an nfsd-authentication cache, we set the flush time to later than last-refresh time in the cache and call cache_flush. The easiest way to find 'later than last-refresh' is 'now+1'. This has two problems. 1/ if the time-of-day clock has gone bacwards, some entries might not be purged 2/ if a new entry is added in the same second as cache_purge ran, it will get ignored. To resolve these issues, we set the flushtime to the maximum possible time before calling cache_flush, and then set it back to the minimum time afterwards. Signed-off-by:Neil Brown <neilb@cse.unsw.edu.au> Signed-off-by:
-
Neil Brown authored
More fall-out from the change to allow multi-page replies to readdir requests. Signed-off-by:
-
Neil Brown authored
Signed-off-by:
-
Neil Brown authored
This is only used by nfsd to save one kmalloc, and the code is not always kept up-to-date with dentry_open, so just get rid of it. Signed-off-by:
-
Bruce Allan authored
Bruce Allan says: The user-specified fsid= export option still doesn't work after the changes made 5 months ago. Below is a patch against 2.6.7 through the recent 2.6.8-rc2-bk13. Signed-off-by:
-
