- 27 Jun, 2004 40 commits
-
-
Andrew Morton authored
Using current gcc CVS I hit a piece of code in which the compiler was emitting a memmove() call. The kernel link failed. Uninline it. Also, move the memcpy and memset exports into memcpy.c. Signed-off-by:
Andrew Morton <akpm@osdl.org> Signed-off-by:
Linus Torvalds <torvalds@osdl.org>
-
Neil Brown authored
Allow the lease to be set from /proc/fs/nfs/nfsv4leasetime. To comply with rfc3530, this appears as a server reboot from the point of view of the client, which must reclaim state with the grace period. From: Andy Adamson <andros@citi.umich.edu> Signed-off-by:
J. Bruce Fields <bfields@citi.umich.edu> Signed-off-by:
Neil Brown <neilb@cse.unsw.edu.au> Signed-off-by:
-
Neil Brown authored
Currently nfs4_arg->to_free keeps a list of void ptrs on which kfree is called when freeing the nfs4_arg. This allows us to do cleanup on e.g. xdr decode failures. To allow more complicated objects to be freed (in particular, acls), we add a "void (*release)(void *)" to allow us to request something other than kfree be called when freeing. Signed-off-by:
-
Neil Brown authored
Preparation for delegations: parse callback information provided in setclientid request. From: Andy Adamson <andros@citi.umich.edu> Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu> Signed-off-by:
-
Neil Brown authored
Insist that the first time a client presents a new lockowner, the seqid should be 0. (RFC 3530 section 8.1.5) Also, return an error if the client presents a previously-used lockowner as if it were new. From: Andy Adamson <andros@citi.umich.edu> Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu> Signed-off-by:
-
Neil Brown authored
nfsd4_proc_compound is using over a thousand bytes of stack. This is partly because it declares two local svc_fh's, partly because of a big switch statement which calls a bunch of functions which may be inlined. Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu> Signed-off-by:
-
Neil Brown authored
Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu> Signed-off-by:
-
Neil Brown authored
Simplify nfsd4_release_lockowner a bit, factor out code that we need for another patch. Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu> Signed-off-by:
-
Neil Brown authored
Use opaque xdr encoding routines from xdr.c instead of rolling our own. Signed-off-by:
-
Neil Brown authored
From: Greg Banks <gnb@sgi.com> NFS/TCP has been used widely for a long time now, and is now enabled by many distros and typically recommended for lossy or congested networks. This patch removes the EXPERIMENTAL tag, updates the help text, and changes arch defconfigs to set it by default (note that several already did so). Signed-off-by:
-
Kenneth W. Chen authored
It adds per node huge page stats in sysfs. Signed-off-by:
-
Robert Picco authored
I eliminated the request_irq brain damage, chopped off procfs support (didn't care for it too much in the first place and it was adopted from rtc.c), made the check for FMODE_WRITE in hpet_open and responded to a few other suggestions. Signed-off-by:
-
Andrey Panin authored
This patch ports APM BIOS driver to new DMI probing API. Signed-off-by:
Andrey Panin <pazke@donpac.ru> Signed-off-by:
-
Andrey Panin authored
BROKEN_ACPI_Sx flag doesn't seem to be used anywhere in the kernel, so ASUS K7V-RM can be removed. Signed-off-by:
-
Andrey Panin authored
This patch ports powernow-k7 driver to new DMI probing API. Signed-off-by:
-
Andrey Panin authored
This patch ports sonypi driver to new DMI probing API and removes is_unsafe_smbus global variable. Signed-off-by:
-
Andrey Panin authored
This patch ports sonypi driver to new DMI probing API and removes is_sony_vaio_laptop global variable. Signed-off-by:
-
Andrey Panin authored
This patch ports PnP BIOS driver to new DMI probing API. Signed-off-by:
-
Andrey Panin authored
This patch moves PCI IRQ routing workaround for Acer TravelMate 360 laptop to arch/i386/pci/irq.c and makes acer_tm360_irqrouting variable static. It also fixes VisWs build error caused by this workaround code. Signed-off-by:
-
Rusty Russell authored
store_stackinfo() does an unlocked module list walk during normal runtime which opens up a race with the module load/unload code. This can be triggered by simply unloading and loading a module in a loop with CONFIG_DEBUG_PAGEALLOC resulting in store_stackinfo() tripping over bad list pointers. kernel_text_address doesn't take any locks, because during an OOPS we don't want to deadlock. Rename that to __kernel_text_address, and make kernel_text_address take the lock. Signed-off-by:
Zwane Mwaikambo <zwane@fsmlabs.com> Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (modified) Signed-off-by:
-
Martin J. Bligh authored
I find __free_pages_bulk very hard to understand ... (I was trying to mod it for the non MAX_ORDER aligned zones, and cleaned it up first). This should make it much more comprehensible to mortal man ... I benchmarked the changes on the big 16x and it's no slower (actually it's about 0.5% faster, but that's within experimental error). I moved the creation of mask into __free_pages_bulk from the caller - it seems to really belong inside there. Then instead of doing wierd limbo dances with mask, I made it use order instead where it's more intuitive. Personally I find this makes the whole thing a damned sight easier to understand. Signed-off-by:
-
Coywolf Qi Hunt authored
I just find a bug that ``make distclean'' cannot remove the editor backup files and the like when using build directory. That is because the find command is improperly searching the build directory instead of the $(srctree) it should. Signed-off-by:
-
Keith Owens authored
Verify that linking kallsyms into vmlinux generates a stable System.map, instead of assuming that it is stable. Add CONFIG_KALLSYMS_EXTRA_PASS as a temporary workaround for unstable maps, so users can proceed while waiting for kallsyms to be fixed. Signed-off-by:
Keith Owens <kaos@sgi.com> Signed-off-by:
-
Keith Owens authored
Exclude symbols added by kallsyms itself, so .tmp_kallsyms[12].S have the same list of symbols. Signed-off-by:
-
Zwane Mwaikambo authored
This is a small cleanup requested by Urban, use the rcls/err in smb_request as opposed to smb_sb_info. Signed-off-by:
Zwane Mwaikambo <zwane@linuxpower.ca> Signed-off-by:
-
Andrew Morton authored
This BUG_ON() triggers for `count = -EFOO' due to PAGE_SIZE being unsigned. Signed-off-by:
-
Ingo Molnar authored
we'd like to announce the availability of the following kernel patch: http://redhat.com/~mingo/nx-patches/nx-2.6.7-rc2-bk2-AE which makes use of the 'NX' x86 feature pioneered in AMD64 CPUs and for which support has also been announced by Intel. (other x86 CPU vendors, Transmeta and VIA announced support as well. Windows support for NX has also been announced by Microsoft, for their next service pack.) The NX feature is also being marketed as 'Enhanced Virus Protection'. This patch makes sure Linux has full support for this hardware feature on x86 too. What does this patch do? The pagetable format of current x86 CPUs does not have an 'execute' bit. This means that even if an application maps a memory area without PROT_EXEC, the CPU will still allow code to be executed in this memory. This property is often abused by exploits when they manage to inject hostile code into this memory, for example via a buffer overflow. The NX feature changes this and adds a 'dont execute' bit to the PAE pagetable format. But since the flag defaults to zero (for compatibility reasons), all pages are executable by default and the kernel has to be taught to make use of this bit. If the NX feature is supported by the CPU then the patched kernel turns on NX and it will enforce userspace executability constraints such as a no-exec stack and no-exec mmap and data areas. This means less chance for stack overflows and buffer-overflows to cause exploits. furthermore, the patch also implements 'NX protection' for kernelspace code: only the kernel code and modules are executable - so even kernel-space overflows are harder (in some cases, impossible) to exploit. Here is how kernel code that tries to execute off the stack is stopped: kernel tried to access NX-protected page - exploit attempt? (uid: 500) Unable to handle kernel paging request at virtual address f78d0f40 printing eip: ... The patch is based on a prototype NX patch written for 2.4 by Intel - special thanks go to Suresh Siddha and Jun Nakajima @ Intel. The existing NX support in the 64-bit x86_64 kernels has been written by Andi Kleen and this patch is modeled after his code. Arjan van de Ven has also provided lots of feedback and he has integrated the patch into the Fedora Core 2 kernel. Test rpms are available for download at: http://redhat.com/~arjanv/2.6/RPMS.kernel/ the kernel-2.6.6-1.411 rpms have the NX patch applied. here's a quickstart to recompile the vanilla kernel from source with the NX patch: http://redhat.com/~mingo/nx-patches/QuickStart-NX.txt update: - make the heap non-executable on PT_GNU_STACK binaries. - make all data mmap()s (and the heap) executable on !PT_GNU_STACK (legacy) binaries. This has no effect on non-NX CPUs, but should be much more compatible on NX CPUs. The only effect it has it has on non-NX CPUs is the extra 'x' bit displayed in /proc/PID/maps. Signed-off-by: -
Stas Sergeev authored
The previous discussion was started here: http://www.uwsg.iu.edu/hypermail/linux/kernel/0211.0/0477.html but in 2.4 times this was kind of problematic. Now, with the lazy bitmap allocation and per-CPU TSS, this will really not drain any resources I think. 8K TSS increase and 8K per process *that does ioperm()* - I think it is not very bad. The reasons why I need that, are described in the URL above. Basically this will allow to use full-screen VESA under dosemu (without LFB though), and this may be also helpfull for the XFree project and some other projects: http://www.uwsg.iu.edu/hypermail/linux/kernel/9807.1/1079.htmlSigned-off-by:
-
Anton Blanchard authored
__alloc_bootmem_node currently panics if it cant satisfy an allocation for a particular node. Thats rather antisocial, we should at the very least return NULL and allow the caller to proceed (eg try another node). A quick look at alloc_bootmem_node usage suggests we should fall back to allocating from other nodes if it fails (as arch/alpha/kernel/pci_iommu.c and arch/x86_64/kernel/setup64.c do). The following patch does that. We fall back to the regular __alloc_bootmem when __alloc_bootmem_node fails, which means all other nodes are checked for available memory. Signed-off-by:
Anton Blanchard <anton@samba.org> Signed-off-by:
-
David Howells authored
This fixes a bit of iSeries code that hadn't been changed to reflect that cpumask_t is now a struct and not an integer type. Signed-off-by:
-
Anton Blanchard authored
rtas.c doesn't call reloc_offset remove comment from rtas.c and extern function declaration Signed-off-by:
Milton Miller <miltonm@bga.com> Signed-off-by:
-
Anton Blanchard authored
Some udbg.c cleanups: - remove some old comments - clean up formatting - remove unused udbg_puthex and udbg_printSP Signed-off-by:
-
Anton Blanchard authored
udbg_read would lock up if ppc_md.udbg_putc didnt exist. Just return 0 and dont lock up instead. Signed-off-by:
-
Anton Blanchard authored
Use vsnprintf/snprintf in udbg.c Signed-off-by:
-
Anton Blanchard authored
- Use 970/970FX instead of GPUL - Add POWER5 and 970FX to systemcfg.h - Create new cpu feature CPU_FTR_MMCRA_SIHV and use it Signed-off-by:
-
Andrew Morton authored
In file included from arch/ppc64/kernel/setup.c:37: include/asm/machdep.h:116: `COMMAND_LINE_SIZE' undeclared here (not in a function) Signed-off-by:
-
Bjorn Helgaas authored
Add support for the EFI/DIG PCDP console discovery table (see http://www.dig64.org/specifications/DIG64_HCDPv20_042804.pdf). This moves the code from drivers/serial/8250_hcdp.[ch] to drivers/firmware/pcdp.[ch], since it's no longer 8250-specific. It also obsoletes CONFIG_SERIAL_8250_HCDP, replacing it with CONFIG_EFI_PCDP (which defaults to Y for ia64). In a nutshell, HCDP tells us "these UARTs are available for use as a console," and it's up to the user to explicitly specify the console device. The kernel can guess in some cases, but not all. The PCDP (aka HCDP v2) tells us what we really want to know, namely, "this UART or VGA device is the console device." (It also has provision for support for new device types.) Signed-off-by:
Bjorn Helgaas <bjorn.helgaas@hp.com> Signed-off-by:
-
bk://linux-scsi.bkbits.net/scsi-for-linus-2.6Linus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
Alan Stern authored
On Wed, 23 Jun 2004, Mike Anderson wrote: > Since SCSI already has the device list it would seem like we would > possibly add a new flag like was done for mode sense. As this is not a > transport issue I would assume we would not want to add flags in > usb/storage, but handle it in the mid-layer as a SCSI protocol > non-compliance. Here is a patch that implements this suggestion. It's rather similar to the one that Javier Marcet wrote back in January, in http://marc.theaimsgroup.com/?l=linux-usb-users&m=107345268526718&w=2Signed-off-by:
Alan Stern <stern@rowland.harvard.edu> Signed-off-by:
James Bottomley <James.Bottomley@SteelEye.com>
-
Guennadi Liakhovetski authored
Signed-off-by:
-
