Hello, In linux-2.6.19.2, do the following lines have bugs in them? It looks like they dereference a user pointer without first being checked by the "access_ok" macro to ensure that they point into userspace. Suhabe ======================== File: sound/isa/sscape.c Lines: 550, 665 Description: The pointer "bb" is dereferenced in the expression "bb->code" without being checked first. Fix: Replace "bb->code" with "&bb->code" ======================== File: block/scsi_ioctl.c L...

Hardware list attached, and config. When scanning disk at the start of the install, exits with "signal 13 (0)" and no log entry. Just as the kvm dies there's a switch from the blue install screen to a white on black screen, and a message displays for a fraction of a sec, unreadably fast. I dount it's hardware, memtest was recently run 12hr, and installs of DragonFlyBSD and FreeBSD work. I have two patches applied, diff also attached. Running qemu user mode works, running xen-install does ...

I don't have any illegal modules for testing, but the resulting kernel looks good (and many other of the drivers in your kernel would break if paravirt_ops wasn't exported). Could it be you compiled the module against a CONFIG_PARAVIRT=y tree and tried to use it with a CONFIG_PARAVIRT=n kernel? cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. ...

This patch removes the broken Gemini support. Signed-off-by: Adrian Bunk <bunk@stusta.de> --- arch/powerpc/kernel/head_32.S | 5 arch/powerpc/platforms/embedded6xx/Kconfig | 9 arch/ppc/Kconfig | 9 arch/ppc/boot/simple/Makefile | 4 arch/ppc/boot/simple/misc.c | 15 arch/ppc/configs/gemini_defconfig | 619 --------------------- arch/ppc/kernel/head.S | 18 arch/ppc/p...

i have tested your patch-queue ontop of rc4-mm1 (trivial reject fixups are below), it builds and boots fine. Acked-by: Ingo Molnar <mingo@elte.hu> Ingo --- drivers/char/nozomi.c | 2 +- drivers/net/qla3xxx.c | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) Index: linux/drivers/char/nozomi.c =================================================================== --- linux.orig/drivers/char/nozomi.c +++ linux/drivers/char/nozomi.c @@ -1378,7 +1378,7 @@ static int n...

ok - great! Ingo -

Remove all traces of "raw devices" support. Signed-off-by: Robert P. J. Day <rpjday@mindspring.com> --- since this feature is listed as being obsolete since 2.6.3 and was scheduled for removal back in Dec of 2005, I figure there wasn't much harm in getting rid of it. i'm trying a "make allyesconfig" build as we speak -- so far, it's moving along nicely. Documentation/feature-removal-schedule.txt | 8 Documentation/ioctl-number.txt | 1 drivers/char/Kcon...

Would not it be worthwhile to merge ipt_TCPMSS and ip6t_TCPMSS to xt_TCPMSS instead? -`J' -- -

The obsolete SA_xxx interrupt flags have been used despite the scheduled removal. Fixup the remaining users in -mm. Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Index: linux-2.6.20-rc4-mm1/arch/i386/kernel/vmitime.c =================================================================== --- linux-2.6.20-rc4-mm1.orig/arch/i386/kernel/vmitime.c +++ linux-2.6.20-rc4-mm1/arch/i386/kernel/vmitime.c @@ -121,12 +121,10 @@ static struct clocksource clocksource_vm static irqreturn_t vmi_timer_i...

This patch fixes core dumps to include the vDSO vma, which is left out now. It removes the special-case core writing macros, which were not doing the right thing for the vDSO vma anyway. Instead, it uses VM_ALWAYSDUMP in the vma; there is no need for the fixmap page to be installed. It handles the CONFIG_COMPAT_VDSO case by making elf_core_dump use the fake vma from get_gate_vma after real vmas in the same way the /proc/PID/maps code does. This changes core dumps so they no longer include the no...

This patch fixes ia32 core dumps on x86_64 to include just one phdr for the vDSO vma. Currently it writes a confused format with two phdrs for the address, one without contents and one with. This patch removes the special-case core writing macros for the ia32 vDSO. Instead, it uses VM_ALWAYSDUMP in the vma. This changes core dumps so they no longer include the non-PT_LOAD phdrs from the vDSO, consistent with fixed native i386 core dumps. Signed-off-by: Roland McGrath <roland@redhat.com>...

This patch uses install_special_mapping for the i386 vDSO setup, consolidating duplicated code. Signed-off-by: Roland McGrath <roland@redhat.com> --- arch/i386/kernel/sysenter.c | 53 +++++++++---------------------------------- 1 files changed, 11 insertions(+), 42 deletions(-) diff --git a/arch/i386/kernel/sysenter.c b/arch/i386/kernel/sysenter.c index 5da7442..bc882a2 100644 --- a/arch/i386/kernel/sysenter.c +++ b/arch/i386/kernel/sysenter.c @@ -70,11 +70,12 @@ void enable_sep_c...

This patch makes x86_64 define arch_vma_name for CONFIG_IA32_EMULATION. This makes the ia32 vDSO mapping appear in /proc/PID/maps with "[vdso]" for ia32 processes, as it does on native i386. Signed-off-by: Roland McGrath <roland@redhat.com> --- arch/x86_64/ia32/syscall32.c | 8 ++++++++ 1 files changed, 8 insertions(+), 0 deletions(-) diff --git a/arch/x86_64/ia32/syscall32.c b/arch/x86_64/ia32/syscall32.c index 3ac9355..59f1fa1 100644 --- a/arch/x86_64/ia32/syscall32.c +++ b/arc...

This patch adds the VM_ALWAYSDUMP flag for vm_flags in vm_area_struct. This provides a clean explicit way to have a vma always included in core dumps, as is needed for vDSO's. Signed-off-by: Roland McGrath <roland@redhat.com> --- fs/binfmt_elf.c | 4 ++++ include/linux/mm.h | 1 + 2 files changed, 5 insertions(+), 0 deletions(-) diff --git a/fs/binfmt_elf.c b/fs/binfmt_elf.c index 7cb2872..6fec8bf 100644 --- a/fs/binfmt_elf.c +++ b/fs/binfmt_elf.c @@ -1178,6 +1178,10 @@ s...

I figured it out! I thought you might be interested --- the reason is the mismatch between the default mount options stored in the superblock on disk and the filesystem features compiled into the kernel. Namely, dumpe2fs on the offending filesystems showed the following default mount options: user_xattr acl but on good filesystems it showed "(none)". So, I used "tune2fs -o ^acl" (and ^user_xattr) to clear these in the superblock and mounted the filesystem --- and now mkdir system call work...

I seem to recall a patch sent to lkml that removed nmi_watchdog functionality from ThinkPads exactly because of this. Something to do with SMBIOS code calling int 10h under SMM, and that it would hang hard if NMIs happened at that time. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -

The name space cleanup of the interrupt request flags (SA_xxx -> IRQF_xxx) left a 6 month grace period for the old deprecated flags. Remove them. Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Index: linux-2.6.20-rc3-mm1/Documentation/feature-removal-schedule.txt =================================================================== --- linux-2.6.20-rc3-mm1.orig/Documentation/feature-removal-schedule.txt +++ linux-2.6.20-rc3-mm1/Documentation/feature-removal-schedule.txt @@ -182,15 +18...

The idea of O_DIRECT is to bypass the pagecache, and the pagecache is what provides the security against reading someone else's data using sparse files or partial-block-IO. -

Thanks. I'll try to get those fixes into 2.6.20... NeilBrown -

From: Simon Budig <simon@budig.de> This change introduces a mapping for LED indicators between the USB HID specification and the Linux input subsystem. The previous code properly mapped the LEDs relevant for Keyboards, but garbeled the remaining ones. With this change all LED enums from the input system get mapped to more or less equivalent LED numbers from the HID specification. This patch also extends the debug output and ensures that the unused bits in a HID report to the device are zero...

This is complete bogus. You simply poked random incorrect registers and happened not to crash the chip, or confuse it, and since you have the For all the wrong reasons I would add. -

All the testing was done via a ssh into the workstation. The console was left as booted into, with the gdm running. The remote nfs4 directory was mounted on "/mnt". After copying the 60+ GB and testing that the keyboard was still functioning, I did not reboot but stayed in the same kernel and pulled the latest git then started bisecting. After recompiling, I moved over to the workstation to reboot it, but the keyboard was not functioning ;( I ran "lsusb" and it displayed all the devices. "d...

Because I haven't finished converting all of the different usages of struct class_device to struct device just yet. When that happens, those links go away, as the /sys/class/foo_class/foo is a symlink itself into the /sys/devices/ tree. If you look in the -mm tree there is a patch for the network devices, and I have patches in my tree (but not -mm) for pcmcia, usb_host, usb_device, and input. These patches still need a bit of work before sending them on to their relative maintainers for accepta...

Hi. I have a few of these entries in my log buffer: vmwrite error: reg 6802 value d19e0464 (err 26626) [<c02413bf>] kvm_mmu_zap_page+0x8f/0x1d7 [<c014c2cb>] __pagevec_free+0x18/0x22 [<c0241517>] free_mmu_pages+0x10/0x81 [<c02415c4>] kvm_mmu_destroy+0x3c/0x56 [<c023f3a3>] kvm_free_vcpu+0x8/0x15 [<c023f429>] kvm_dev_release+0x13/0x37 [<c01640c9>] __fput+0xa5/0x14d [<c0161cb1>] filp_close+0x51/0x58 [<c012104b>] put_files_struct+0x5f/0x...

vmalloc space is limited; you really can't assume you can get any more than 64Mb or so (and even then it's thight on some systems already); it really sounds like vmalloc space isn't the right solution for your problem whatever it is (context is lost in the quoted mail)... can you restate the problem to see if there's a better solution possible? Greetings, Arjan van de Ven -- if you want to mail me at work (you don't), use arjan (at) linux.intel.com Test the interaction between Linux and yo...