- 17 Apr, 2004 40 commits
-
-
Alexander Viro authored
The field in question is a) unused b) damn next to impossible to use correctly, due to struct super_block lifetime and locking rules.
-
bk://bk.arm.linux.org.uk/linux-2.6-pcmciaLinus 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
-
Russell King authored
Update serial to use new module parameters rather than MODULE_PARM.
-
Russell King authored
-
bk://bk.arm.linux.org.uk/linux-2.6-rmkLinus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
Russell King authored
This adds detailed documentation concerning how we map the Linux page table structure onto the hardware tables on ARM. In addition, it also adds documentation describing how we emulate the "dirty" and "young" or "accessed" page table bits. This should be of interest to Linux MM developers.
-
Pavel Roskin authored
Patch from: Pavel Roskin As it turns out, mixing MODULE_PARM and module_param in one module is wrong. The parameters specified in module_param are ignored. I've just posted a patch to LKML that will detect this condition and warn about it. The new debugging code used the new-style module_param, which means that all instances of MODULE_PARM should be converted. The attached patch does that. An additional bonus is that module_param_array provides the number of array elements. This allowed me to change tcic.c and i82365.c to use this number for IRQ list. This change was tested with i82365. If "irq_list" is not specified, irq_list_count is 0. I set all permissions to 0444 to be safe. I think we have no secrets from the users regarding those parameters. If some parameters can be changed safely at the runtime, the permissions could be changed to 0644. I didn't examine how safe (and how useful) it would be, so it's 0444 for now.
-
Andrew Morton authored
From: William Lee Irwin III <wli@holomorphy.com> rmk mentioned that ARM was borked as the relation, assumed by generic rmap, PTRS_PER_PTE*sizeof(pte_t) == PAGE_SIZE, fails to hold. The following patch, developed jointly with him (or depending on POV, by him with me acting as codemonkey), is reported to resolve the issue. Specifically, while ARM dedicates an entire PAGE_SIZE -sized block of memory to each PTE table, the PTE table itself only spans half that, the remainder being dedicated to hardware-interpreted structures. As the hardware structure must be contiguous, wider ptes can't be used. So the core-visible PTE table only spans PAGE_SIZE/2 bytes, violating the assumption. This corrects masking and scaling done in ptep_to_address().
-
Andrew Morton authored
From: Dave Jones <davej@redhat.com>
-
Andrew Morton authored
From: Manfred Spraul <manfred@colorfullife.com> Any user can delete any entries in a mqueue mounted filesystem. The attached patch prevents that. - remove the writable test from mq_unlink. - set the sticky bit in the root inode. This affects both mq_unlink and sys_unlink: only the owner (and root) should be allowed to remove queues.
-
Andrew Morton authored
From: David Gibson <david@gibson.dropbear.id.au> Some versions of follow_huge_addr() and follow_huge_pmd() are doing a get_page() on the target page. They shouldn't: follow_page() returns an unpinned page and it is the caller's responsibility to pin the page (if desired) before dropping page_table_lock.
-
Andrew Morton authored
From: David Gibson <david@gibson.dropbear.id.au> Trivial cleanup to flush_hash_hugepage() in the ppc64 hugepage code.
-
Andrew Morton authored
From: Geert Uytterhoeven <geert@linux-m68k.org> While compiling drivers/char/ipmi/ipmi_si_intf.c in 2.6.6-rc1 on m68k, I noticed a missing include (needed for disable_irq_nosync() and enable_irq())
-
Andrew Morton authored
From: "Randy.Dunlap" <rddunlap@osdl.org> floppy98.c (along with other PC-9800 files) has not been updated lately. It won't build currently (2.6.5). This patch makes floppy98 build cleanly.
-
Andrew Morton authored
From: Chris Mason <mason@suse.com> Get rid of the last sleep_on in the reiserfs code
-
Andrew Morton authored
From: Chris Mason <mason@suse.com> Updates the reiserfs-logging improvements to use schedule_timeout instead of yield when letting the transaction grow a little before forcing a commit for fsync/O_SYNC/O_DIRECT. Also, when one process forces a transaction to end and plans on doing the commit (like fsync), it sets a flag on the transaction so the journal code knows not to bother kicking the journal work queue. queue_delayed_work is used so that if we get a bunch of tiny transactions ended quickly, we aren't constantly kicking the work queue. These significantly improve reiserfs performance during fsync heavy workloads.
-
Andrew Morton authored
From: Bart Samwel <bart@samwel.tk> Add support for value 0 to the commit option of reiserfs. Means "restore to the default value". For the maximum commit age, this default value is normally read from the journal; this patch adds an extra variable to cache the default value for the maximum commit age.
-
Andrew Morton authored
From: David Gibson <david@gibson.dropbear.id.au> This is a small cleanup to the PPC64 hugepage code. It removes an unhelpful function, removing some studlyCaps in the process. It was originally this way to match the normal page path, but that has all been rewritten since.
-
Andrew Morton authored
From: Jakub Jelinek <jakub@redhat.com> The first change removes just a useless put_user (si_int and si_ptr are part of the same union, si_ptr is on all arches covering whole union), the rest is fixes for signal handling of SI_MESGQ.
-
Andrew Morton authored
From: Jeff Garzik <jgarzik@pobox.com> It was debug code, no longer required.
-
Andrew Morton authored
From: Bjorn Helgaas <bjorn.helgaas@hp.com> This consolidates the PCI MSI configuration into drivers/pci/Kconfig, removing it from the i386, x86_64, and ia64 Kconfig. It also changes the default for ia64 from "y" to "n". The default on i386 is "n" already, and I'm not sure why ia64 should be different.
-
Andrew Morton authored
From: Jeff Garzik <jgarzik@pobox.com> Nobody ever checks the return value of submit_bh(), and submit_bh() is the only caller that checks the submit_bio() return value. This changes the kernel I/O submission path -- a fast path -- so this cleanup is also a microoptimization.
-
Andrew Morton authored
From: NeilBrown <neilb@cse.unsw.edu.au> From: "J. Bruce Fields" <bfields@fieldses.org> From: Andros: Implement server-side reboot recovery (server now handles open and lock reclaims). Not completely to spec: we don't yet store the state in stable storage that would be required to recover correctly in certain situations.
-
Andrew Morton authored
From: NeilBrown <neilb@cse.unsw.edu.au> The credentials (uid/gid) of a process are set when a filehandle is verified. Nfsv4 allows requests without an explicit filehandle (instead, an implicit 'root' filehandle) so we much make sure the credentials are set for these requests too. From: "J. Bruce Fields" <bfields@fieldses.org> From: Andros: added a call to nfsd_setuser in nfsd4_putrootfh so that nfsd runs as the rpc->cred user.
-
Andrew Morton authored
From: NeilBrown <neilb@cse.unsw.edu.au> From: "J. Bruce Fields" <bfields@fieldses.org> From: Andros: Hold state_lock longer so the stateowner doesn't diseappear out from under us before we get the chance to encode the replay. Don't attempt to save replay if we failed to find a stateowner.
-
Andrew Morton authored
From: NeilBrown <neilb@cse.unsw.edu.au> From: "J. Bruce Fields" <bfields@fieldses.org> From: Andros: locku replies should be saved for possible replay as well.
-
Andrew Morton authored
From: NeilBrown <neilb@cse.unsw.edu.au> From: "J. Bruce Fields" <bfields@fieldses.org> From: Andros: Idea is to keep around a list of openowners recently released by closes, and make sure they stay around long enough so that replays still work.
-
Andrew Morton authored
From: NeilBrown <neilb@cse.unsw.edu.au> From: "J. Bruce Fields" <bfields@fieldses.org> Error return when the client supplies a bad service should be badcred.
-
Andrew Morton authored
From: NeilBrown <neilb@cse.unsw.edu.au> From: "J. Bruce Fields" <bfields@fieldses.org> Fix out-of-spec errors in nfs4 readdir. Add checks for bad cookie values. (plus compile fix from akpm)
-
Andrew Morton authored
From: Kevin Corry <kevcorry@us.ibm.com> Striped: Use an EMIT macro in the status function.
-
Andrew Morton authored
From: Kevin Corry <kevcorry@us.ibm.com> dm-ioctl.c::retrieve_status(): Prevent overrunning the ioctl buffer by making sure we don't call the target status routine with a buffer size limit of zero. [Kevin Corry, Alasdair Kergon]
-
Andrew Morton authored
From: Kevin Corry <kevcorry@us.ibm.com> Clarify the comment regarding the "next" field in struct dm_target_spec. The "next" field has different behavior if you're performing a DM_TABLE_STATUS command than it does if you're performing a DM_TABLE_LOAD command. See populate_table() and retrieve_status() in drivers/md/dm-ioctl.c for more details on how this field is used.
-
Andrew Morton authored
From: Kevin Corry <kevcorry@us.ibm.com> Correctly align the dm_target_spec structures during retrieve_status().
-
Andrew Morton authored
From: Kevin Corry <kevcorry@us.ibm.com> Log an error if the target has unknown target type, or zero length.
-
Andrew Morton authored
From: Kevin Corry <kevcorry@us.ibm.com> dm.c: Use wake_up() rather than wake_up_interruptible() with the eventq.
-
Andrew Morton authored
From: Kevin Corry <kevcorry@us.ibm.com> Handle interrupts within suspend.
-
Andrew Morton authored
From: Kevin Corry <kevcorry@us.ibm.com> Check the uptodate flag in sub-bios to see if there was an error. [Mike Christie]
-
Andrew Morton authored
From: Kevin Corry <kevcorry@us.ibm.com> Fix 64/32 bit ioctl problems.
-
Petr Vandrovec authored
The recent controlling terminal changes broke exec from multithreaded application because de_thread was not upgraded to new arrangement. I know that I should not have LD_PRELOAD library which automatically creates one thread, but it looked like a cool solution to the problem I had. de_thread must initialize the controlling terminal information in the new thread group.
-