The changelog for commit d6dd61c831226f9cd7750885da04d360d6455101 says arch_dup_mmap, which is called when a new mmap is created at fork Is there a reason that you're not tracking mm creation in exec? Jeff -

On Tue, 13 Nov 2007 18:30:30 +0100 (CET) that's pretty peculiar. We'd only expect to see atomics being used in conjunction with atomic_add/sub/inc/etc. Here the driver is using an atomic_t as a state variable. And here's the magic bit: spin_lock_irqsave(&ucs->lock, flags); state = atomic_read(&ucs->basstate); atomic_set(&ucs->basstate, (state & ~clear) | set); spin_unlock_irqrestore(&ucs->lock, flags); I'm suspecting that a plain old `int' would be more a...

The normal situation on the memory is side is that most of the memory is in use, but some pages are ready to be discarded, they're just kept around because we have nothing better to do (yet) with that page. Is there a tool to do something similar with file systems. I have a lot of unimportant files in my file-system, typically browser caches and things like that, which can be thrown away without any risk of losing data. I just keep them around because I have nothing better to do with my disk sp...

Subject: [PATCH] x86: clean up nmi_32/64.c clean up and make nmi_32/64.c more similar. - white space and coding style clean up. - nmi_cpu_busy is available on CONFIG_SMP. - move functions __acpi_nmi_enable, acpi_nmi_enable, __acpi_nmi_disable and acpi_nmi_disable. - make variables name more similar. Signed-off-by: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com> --- arch/x86/kernel/nmi_32.c | 18 +++++---- arch/x86/kernel/nmi_64.c | 92 +++++++++++++++++++++++----------------------- ...

IIRC, the present bit is ignored in the magic 4-entry PGD. All entries have to be present. What earlier CPU's did was to basically load all four values into the CPU when you loaded %cr3. There was no "three-level page table walker" at all: it was still a two-level page table walker, there were just for magic internal page tables that were indexed off the two high bits. Linus -

_PAGE_PCD maps a page with caching disabled, which is typically used for mapping harware registers. Xen never allows it to be set on a mapping, and unprivileged guests never need it since they can't see the real underlying hardware. However, some uncached mappings are made early when probing the (non-existent) APIC, and its OK to mask off the PCD flag in these cases. This became necessary because Xen started checking for this bit, rather than silently masking it off. Signed-off-by: Jeremy Fitz...

Greetings all, It is my great pleasure to announce that the Linux-iSCSI.org project has reached its first 2.9-BETA release and its now offering the ability to build source against any RPM or DEB based kernel and distribution. The Linux-iSCSI.org West cluster is offering binaries for CentOS 5 and Debian 4, and instructions are now online. This project provides the infrastructure pieces required to run a production IP storage fabric, and is constantly evolving. The complete target stack, which i...

I got a report from a user this morning with the following oops. Unable to handle kernel NULL pointer dereference at 0000000000000038 RIP: [<ffffffff810ad479>] iput+0x18/0x7b PGD 6fdf9067 PUD 7810c067 PMD 0 Oops: 0000 [1] SMP CPU 1 Modules linked in: berry_charge tun vfat fat usb_storage appletalk ipx p8023 i915 drm dcdbas ipt_MASQUERADE iptable_nat nf_nat bridge rfcomm l2cap autofs4 sunrpc nf_conntrack_netbios_ns ipt_REJECT nf_conntrack_ipv4 xt_state nf_conntrack nfnetlink iptable_filter ip_...

This patch does fix potential NULL pointer dereference that could take place inside of strcmp() if of_get_property() call failed. Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com> --- arch/powerpc/platforms/83xx/usb.c | 8 ++++---- 1 files changed, 4 insertions(+), 4 deletions(-) diff --git a/arch/powerpc/platforms/83xx/usb.c b/arch/powerpc/platforms/83xx/usb.c index eafe760..b45160f 100644 --- a/arch/powerpc/platforms/83xx/usb.c +++ b/arch/powerpc/platforms/83xx/usb.c @@ -130,7...

<SNIP> Hi Steve, Not sure I've ever posted on this list. Always looking to help out at my low level. Anyway, I tried building the kernel. My 1st two attempts, done running make menuconfig from scratch, didn't boot. I gave up on that for now and tried using make oldconfig from my 2.6.23-rt1 kernel (I'm so far behind!!) and ended up with this error. Not sure it's enough for you to find the bug. If you want/need more or want the config file let me know. I'm sure this is just me s...

Sent. -

Hello Ulrich, Regards, Frederik -

weird - i built it on 32-bit and it should have failed the build? Ingo -

This part adds support for sys_indirect on UML on x86 and x86-64. indirect.h | 6 ++++++ 1 file changed, 6 insertions(+) --- /dev/null 2007-09-23 16:36:38.465394704 -0700 +++ b/include/asm-um/indirect.h 2007-11-15 09:56:23.000000000 -0800 @@ -0,0 +1,6 @@ +#ifndef __UM_INDIRECT_H +#define __UM_INDIRECT_H + +#include "asm/arch/indirect.h" + +#endif -

This is the actual architecture-independent part of the system call implementation. b/include/linux/indirect.h | 13 ++++++++++++ b/include/linux/syscalls.h | 3 ++ b/kernel/Makefile | 2 - b/kernel/indirect.c | 46 +++++++++++++++++++++++++++++++++++++++++++++ include/linux/sched.h | 4 +++ 5 files changed, 67 insertions(+), 1 deletion(-) --- a/include/linux/sched.h +++ b/include/linux/sched.h @@ -80,6 +80,7 @@ struct sched_param { #include <linux/rcupd...

Patch is valid only for 2.6.23.x, guessing from the recent arch/ changes in 2.6.24-rc. set_rtc_mmss() was used to be called from interrupt context in 2.6.22, however in 2.6.23, it is called from a timer context, where interrupts are enabled. This patch ensures that rtc_interrupt() won't dead-lock with set_rtc_mmss(). -- BUG: spinlock recursion on CPU#1, swapper/0 lock: ffffffff8063ffe0, .magic: dead4ead, .owner: swapper/0, .owner_cpu: 1 Call Trace: <IRQ> [<ffffffff80361297>]...

The following patches provide an alternative implementation of the sys_indirect system call which has been discussed a few times. This no system call allows us to extend existing system call interfaces with adding more system calls. Davide's previous implementation is IMO far more complex than warranted. This code here is trivial, as you can see. I've discussed this approach with Linus last week and for a brief moment we actually agreed on something. We pass an additional block of data to the ...

Yes, I mentioned this to Ulrich as one of the things that would make sense. Uli doesn't care that much about async syscalls, but I think that from a kernel standpoint, we'd want to use this same indirect call for async scheduling, rather than have two separate interfaces (because async scheduling will want to have all the same flags intefaces for open/socket/etc *too* and a doubly-indirect setup would be insanity!) And it definitely fits the bill as a really simple syslet model for the...

I probably won't come around to trying sys_indirect with syslets until next week, so it's probably fine for me to just wait for you to get v3 out. (and I'm more likely to test native i386 or x86_64 anyway, so.. :)) - z -

This is the actual architecture-independent part of the system call implementation. b/include/linux/indirect.h | 13 +++++++++++++ b/include/linux/syscalls.h | 3 +++ b/kernel/Makefile | 2 +- b/kernel/indirect.c | 25 +++++++++++++++++++++++++ b/include/linux/sched.h | 4 ++++ 5 files changed, 46 insertions(+), 1 deletion(-) --- a/include/linux/sched.h +++ b/include/linux/sched.h @@ -80,6 +80,7 @@ struct sched_param { #include <linux/rcupdate.h> #i...

[ Ingo, Thomas - see the whole series on linux-kernel ] The thing is, not all system calls can do this. Some system calls are magic, and don't just take the arguments in registers: they also care about the actual stack pointer and the whole pt_regs struct when returning to user mode. So this does need more infrastructure: some way of marking which system calls cannot be executed indirectly. The magic system calls are things like: - sys_iopl() - this one changes the eflags value re...

The x86 unification resulted in CONFIG_X86_HT no longer being set if (X86_32 && MK8). After grep'ing through the tree I think the problem is that different places have different assumptions about the semantics of CONFIG_X86_HT, either: - hyperthreading or - multicore and the SCHED_SMT and SCHED_MC dependencies are just one of the symptoms. This should be sorted out properly, but until then we should keep the 2.6.23 status quo. Signed-off-by: Adrian Bunk <bunk@kernel.org> ...

After looking what does what and fixing it. Right now this patch is not a 1:1 replacement of the .23 status quo, as it now makes SCHED_SMT and SCHED_HT depend on !MK8 for 64bit. tglx -

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. Pearl S. Buck - Dragon Seed -

proc symlinks always have valid ->data containing destination of symlink. No need to check it on removal -- proc_symlink() already done it. Signed-off-by: Alexey Dobriyan <adobriyan@sw.ru> --- fs/proc/generic.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- a/fs/proc/generic.c +++ b/fs/proc/generic.c @@ -704,7 +704,7 @@ void free_proc_entry(struct proc_dir_entry *de) release_inode_number(ino); - if (S_ISLNK(de->mode) && de->data) + if (S_ISLNK(d...