Andi Kleen (on Mon, 13 Aug 2007 15:08:45 +0200) wrote:
>On Mon, Aug 13, 2007 at 12:33:05PM +0100, Jan Beulich wrote:
>
>
>>
>> if (cpu_has_ds) {
>> unsigned int l1;
>> --- linux-2.6.23-rc3/arch/i386/kernel/traps.c2007-08-13
>> 08:59:45.0 +0200
>> +++
Originally sent to the maintainer of the i386 math-emu code
([EMAIL PROTECTED]) but that mail was bounced[1]. Is anybody
maintaining the math-emu code and do we even care about it anymore?
I am doing static code analysis on the kernel and have found a stack
imbalance in
Originally sent to the maintainer of the i386 math-emu code
([EMAIL PROTECTED]) but that mail was bounced[1]. Is anybody
maintaining the math-emu code and do we even care about it anymore?
I am doing static code analysis on the kernel and have found a stack
imbalance in
Andi Kleen (on Mon, 13 Aug 2007 15:08:45 +0200) wrote:
On Mon, Aug 13, 2007 at 12:33:05PM +0100, Jan Beulich wrote:
if (cpu_has_ds) {
unsigned int l1;
--- linux-2.6.23-rc3/arch/i386/kernel/traps.c2007-08-13
08:59:45.0 +0200
+++
Mathieu Desnoyers (on Sun, 12 Aug 2007 10:54:43 -0400) wrote:
>Add the primitives cmpxchg_local, cmpxchg64 and cmpxchg64_local to ia64. They
>use cmpxchg_acq as underlying macro, just like the already existing ia64
>cmpxchg().
>
>Signed-off-by: Mathieu Desnoyers <[EMAIL PROTECTED]>
>CC: [EMAIL
Mathieu Desnoyers (on Sun, 12 Aug 2007 10:54:43 -0400) wrote:
Add the primitives cmpxchg_local, cmpxchg64 and cmpxchg64_local to ia64. They
use cmpxchg_acq as underlying macro, just like the already existing ia64
cmpxchg().
Signed-off-by: Mathieu Desnoyers [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
Casey Schaufler (on Sat, 11 Aug 2007 10:57:31 -0700) wrote:
>Smack is the Simplified Mandatory Access Control Kernel.
>
> [snip]
>
>Smack defines and uses these labels:
>
>"*" - pronounced "star"
>"_" - pronounced "floor"
>"^" - pronounced "hat"
>"?" - pronounced "huh"
>
>The
Casey Schaufler (on Sat, 11 Aug 2007 12:56:42 -0700 (PDT)) wrote:
>
>--- Arjan van de Ven <[EMAIL PROTECTED]> wrote:
>> > +#include
>> > +#include
>> > +#include
>> > +#include
>> > +#include
>> > +#include "../../net/netlabel/netlabel_domainhash.h"
>>
>> can't you move this header to
Casey Schaufler (on Sat, 11 Aug 2007 12:56:42 -0700 (PDT)) wrote:
--- Arjan van de Ven [EMAIL PROTECTED] wrote:
+#include linux/kernel.h
+#include linux/vmalloc.h
+#include linux/security.h
+#include linux/mutex.h
+#include net/netlabel.h
+#include
Casey Schaufler (on Sat, 11 Aug 2007 10:57:31 -0700) wrote:
Smack is the Simplified Mandatory Access Control Kernel.
[snip]
Smack defines and uses these labels:
* - pronounced star
_ - pronounced floor
^ - pronounced hat
? - pronounced huh
The access rules enforced by Smack
Eric W. Biederman (on Fri, 03 Aug 2007 06:36:23 -0600) wrote:
>
>Well we currently keep a struct thread_info on the stack
>which while not as bad as task_struct has it's own uses
>and implications which may limit what you are trying
>to do.
Not an issue. We already copy struct thread_info when
Eric W. Biederman (on Fri, 03 Aug 2007 06:36:23 -0600) wrote:
Well we currently keep a struct thread_info on the stack
which while not as bad as task_struct has it's own uses
and implications which may limit what you are trying
to do.
Not an issue. We already copy struct thread_info when
Andrew Morton (on Thu, 2 Aug 2007 23:25:02 -0700) wrote:
>On Fri, 03 Aug 2007 14:05:47 +1000 Keith Owens <[EMAIL PROTECTED]> wrote:
Switching to [EMAIL PROTECTED], I just resigned from SGI.
>> I have pretty well given up on RAS code in the Linux kernel. Everybody
>>
Andrew Morton (on Thu, 2 Aug 2007 23:25:02 -0700) wrote:
On Fri, 03 Aug 2007 14:05:47 +1000 Keith Owens [EMAIL PROTECTED] wrote:
Switching to [EMAIL PROTECTED], I just resigned from SGI.
I have pretty well given up on RAS code in the Linux kernel. Everybody
has different ideas
First a bit of background for people who are not familiar with kernel
stack constructs.
* Every process has a dedicated kernel stack. In this context,
'process' includes user space processes and threads, plus those
processes that only exist inside the kernel (e.g. kswapd, xfslogd).
* When a
;> Possibly.
>>
>> > BTW, I use kdb and lkcd now, but I want to use kdb and kdump. I sent a
>> > patch to
>> > kdb community but it was rejected. kdb maintainer Keith Owens said,
>>
>> >> Both KDB and crash_kexec should be using the panic_notifier_chain, with
or they
don't notice this problem yet. I think they will be in trouble if all
distributions choose only kdump.
Possibly.
BTW, I use kdb and lkcd now, but I want to use kdb and kdump. I sent a
patch to
kdb community but it was rejected. kdb maintainer Keith Owens said,
Both KDB
First a bit of background for people who are not familiar with kernel
stack constructs.
* Every process has a dedicated kernel stack. In this context,
'process' includes user space processes and threads, plus those
processes that only exist inside the kernel (e.g. kswapd, xfslogd).
* When a
Trent Piepho (on Tue, 24 Jul 2007 19:31:36 -0700 (PDT)) wrote:
>Adding __builtin_trap after the
>asm might be an ok fix. It will emit a spurious int 6, but that won't even be
>reached since the asm doesn't return, and it probably be less extra code than
>the loop.
int 6 is a two byte
Trent Piepho (on Tue, 24 Jul 2007 19:31:36 -0700 (PDT)) wrote:
Adding __builtin_trap after the
asm might be an ok fix. It will emit a spurious int 6, but that won't even be
reached since the asm doesn't return, and it probably be less extra code than
the loop.
int 6 is a two byte instruction,
Bernardo Innocenti (on Thu, 17 May 2007 02:36:21 -0400) wrote:
>Keith Owens wrote:
>
>> Before using MSR, you must first check that the cpu supports the
>> instruction, rd/wrmsr cause an oops on 486 or earlier. Also using an
>> invalid msr number causes an oops, so u
/modules/kdbm_x86.c| 59 ++
7 files changed, 85 insertions(+), 10 deletions(-)
diff -u linux/arch/i386/kdb/ChangeLog linux/arch/i386/kdb/ChangeLog
--- linux/arch/i386/kdb/ChangeLog
+++ linux/arch/i386/kdb/ChangeLog
@@ -1,3 +1,9 @@
+2007-05-17 Kei
/kdb/ChangeLog linux/arch/i386/kdb/ChangeLog
--- linux/arch/i386/kdb/ChangeLog
+++ linux/arch/i386/kdb/ChangeLog
@@ -1,3 +1,9 @@
+2007-05-17 Keith Owens [EMAIL PROTECTED]
+
+ * Update dumpregs comments for rdmsr and wrmsr commands.
+ Bernardo Innocenti.
+ * kdb v4.4-2.6.21-i386-3
Bernardo Innocenti (on Thu, 17 May 2007 02:36:21 -0400) wrote:
Keith Owens wrote:
Before using MSR, you must first check that the cpu supports the
instruction, rd/wrmsr cause an oops on 486 or earlier. Also using an
invalid msr number causes an oops, so use rd/wrmsr_safe().
I didn't bother
Fernando Luis =?ISO-8859-1?Q?V=E1zquez?= Cao (on Wed, 25 Apr 2007 20:13:28
+0900) wrote:
>+static __inline__ unsigned long safe_apic_wait_icr_idle(void)
>+{
>+ unsigned long send_status;
>+ int timeout;
>+
>+ timeout = 0;
>+ do {
>+ udelay(100);
>+
Fernando Luis =?ISO-8859-1?Q?V=E1zquez?= Cao (on Wed, 25 Apr 2007 20:13:28
+0900) wrote:
+static __inline__ unsigned long safe_apic_wait_icr_idle(void)
+{
+ unsigned long send_status;
+ int timeout;
+
+ timeout = 0;
+ do {
+ udelay(100);
+ send_status
Dave Jones (on Thu, 22 Mar 2007 01:37:14 -0400) wrote:
>On Thu, Mar 22, 2007 at 04:26:39PM +1100, Keith Owens wrote:
> > Dave Jones (on Thu, 22 Mar 2007 01:15:25 -0400) wrote:
> > >make help implies that supplying $CHECK on the command line
> > >should override spar
Dave Jones (on Thu, 22 Mar 2007 01:15:25 -0400) wrote:
>make help implies that supplying $CHECK on the command line
>should override sparse as the checker used when building with C=1
>Yet, this doesn't seem to be the case.
>
>This would be useful for cases where for eg, sparse isn't in
>the $PATH,
Bjorn Helgaas (on Wed, 21 Mar 2007 10:35:38 -0600) wrote:
>On Tuesday 20 March 2007 08:32, Bjorn Helgaas wrote:
>> On Tuesday 20 March 2007 00:46, Keith Owens wrote:
>> > Booting with 'console=tty console=ttyS0,9600'. The serial console on
>> > ttyS0 (0x3f8, irq 4)
Rusty Russell (on Thu, 22 Mar 2007 14:52:29 +1100) wrote:
>On Thu, 2007-03-22 at 14:24 +1100, Rusty Russell wrote:
>> Belay this: there's a X86_EFLAGS_IF in asm/processor.h which we should
>> use. Will send patch.
>
>How's this. There may be other users, but they're not easy to grep for.
One
Bjorn Helgaas (on Wed, 21 Mar 2007 10:35:38 -0600) wrote:
On Tuesday 20 March 2007 08:32, Bjorn Helgaas wrote:
On Tuesday 20 March 2007 00:46, Keith Owens wrote:
Booting with 'console=tty console=ttyS0,9600'. The serial console on
ttyS0 (0x3f8, irq 4) is probed twice, once from
Dave Jones (on Thu, 22 Mar 2007 01:15:25 -0400) wrote:
make help implies that supplying $CHECK on the command line
should override sparse as the checker used when building with C=1
Yet, this doesn't seem to be the case.
This would be useful for cases where for eg, sparse isn't in
the $PATH,
Dave Jones (on Thu, 22 Mar 2007 01:37:14 -0400) wrote:
On Thu, Mar 22, 2007 at 04:26:39PM +1100, Keith Owens wrote:
Dave Jones (on Thu, 22 Mar 2007 01:15:25 -0400) wrote:
make help implies that supplying $CHECK on the command line
should override sparse as the checker used when building
Rusty Russell (on Thu, 22 Mar 2007 14:52:29 +1100) wrote:
On Thu, 2007-03-22 at 14:24 +1100, Rusty Russell wrote:
Belay this: there's a X86_EFLAGS_IF in asm/processor.h which we should
use. Will send patch.
How's this. There may be other users, but they're not easy to grep for.
One less set
Dell SC1425 x86_64 running in i386 mode (the problem also occurs in
x86_64 mode). Kernel 2.6.21-rc4, gcc 4.1.0. Config extract at end.
Booting with 'console=tty console=ttyS0,9600'. The serial console on
ttyS0 (0x3f8, irq 4) is probed twice, once from serial8250_init() and
again from
Dell SC1425 x86_64 running in i386 mode (the problem also occurs in
x86_64 mode). Kernel 2.6.21-rc4, gcc 4.1.0. Config extract at end.
Booting with 'console=tty console=ttyS0,9600'. The serial console on
ttyS0 (0x3f8, irq 4) is probed twice, once from serial8250_init() and
again from
Willy Tarreau (on Fri, 1 Dec 2006 06:26:53 +0100) wrote:
>On Fri, Dec 01, 2006 at 04:14:04PM +1100, Keith Owens wrote:
>> SuSE's SLES10 ships with gcc 4.1.0. There is nothing to stop a
>> distributor from backporting the bug fix from gcc 4.1.1 to 4.1.0, but
>> this patch woul
Andrew Morton (on Thu, 30 Nov 2006 21:05:51 -0800) wrote:
>On Wed, 29 Nov 2006 21:14:10 +0100
>Willy Tarreau <[EMAIL PROTECTED]> wrote:
>
>> Then why not simply check for gcc 4.1.0 in compiler.h and refuse to build
>> with 4.1.0 if it's known to produce bad code ?
>
>Think so. I'll queue this and
Andrew Morton (on Thu, 30 Nov 2006 21:05:51 -0800) wrote:
On Wed, 29 Nov 2006 21:14:10 +0100
Willy Tarreau [EMAIL PROTECTED] wrote:
Then why not simply check for gcc 4.1.0 in compiler.h and refuse to build
with 4.1.0 if it's known to produce bad code ?
Think so. I'll queue this and see how
Willy Tarreau (on Fri, 1 Dec 2006 06:26:53 +0100) wrote:
On Fri, Dec 01, 2006 at 04:14:04PM +1100, Keith Owens wrote:
SuSE's SLES10 ships with gcc 4.1.0. There is nothing to stop a
distributor from backporting the bug fix from gcc 4.1.1 to 4.1.0, but
this patch would not allow the fixed
David Miller (on Tue, 28 Nov 2006 20:04:53 -0800 (PST)) wrote:
>From: Keith Owens
>Date: Wed, 29 Nov 2006 14:56:20 +1100
>
>> Secondly, I believe that this is a separate problem from bug 22278.
>> hpet_readl() is correctly using volatile internally, but its result is
>&g
Nicholas Miell (on Tue, 28 Nov 2006 19:08:25 -0800) wrote:
>On Wed, 2006-11-29 at 13:22 +1100, Keith Owens wrote:
>> Compiling 2.6.19-rc6 with gcc version 4.1.0 (SUSE Linux),
>> wait_hpet_tick is optimized away to a never ending loop and the kernel
>> hangs on boot in timer s
jmp1d
This is not a problem with gcc 3.3.5. Adding barrier() calls to
wait_hpet_tick does not help, making the variables volatile does.
Signed-off-by: Keith Owens
---
arch/i386/kernel/time_hpet.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux-2.6/arch/i386/kernel
jmp1d wait_hpet_tick+0x3
This is not a problem with gcc 3.3.5. Adding barrier() calls to
wait_hpet_tick does not help, making the variables volatile does.
Signed-off-by: Keith Owens kaos@ocs.com.au
---
arch/i386/kernel/time_hpet.c |2 +-
1 file changed, 1 insertion(+), 1
Nicholas Miell (on Tue, 28 Nov 2006 19:08:25 -0800) wrote:
On Wed, 2006-11-29 at 13:22 +1100, Keith Owens wrote:
Compiling 2.6.19-rc6 with gcc version 4.1.0 (SUSE Linux),
wait_hpet_tick is optimized away to a never ending loop and the kernel
hangs on boot in timer setup.
001a
David Miller (on Tue, 28 Nov 2006 20:04:53 -0800 (PST)) wrote:
From: Keith Owens kaos@ocs.com.au
Date: Wed, 29 Nov 2006 14:56:20 +1100
Secondly, I believe that this is a separate problem from bug 22278.
hpet_readl() is correctly using volatile internally, but its result is
being assigned
The new ia64 MCA/INIT handlers[1] (think of them as super NMI) run on
separate stacks. 99% of the changes for these new handlers is ia64
only code, however they need a couple of scheduler hooks to support
these extra stacks. The complete patch set will be coming through the
ia64 tree, this RFC
The new ia64 MCA/INIT handlers[1] (think of them as super NMI) run on
separate stacks. 99% of the changes for these new handlers is ia64
only code, however they need a couple of scheduler hooks to support
these extra stacks. The complete patch set will be coming through the
ia64 tree, this RFC
On Mon, 29 Aug 2005 09:12:08 -0700,
Tom Rini <[EMAIL PROTECTED]> wrote:
>
>This adds hardware breakpoint support for i386. This is not as well tested as
>software breakpoints, but in some minimal testing appears to be functional.
Hardware breakpoints must be per cpu, not global. Also you will
On Mon, 29 Aug 2005 09:12:08 -0700,
Tom Rini [EMAIL PROTECTED] wrote:
This adds hardware breakpoint support for i386. This is not as well tested as
software breakpoints, but in some minimal testing appears to be functional.
Hardware breakpoints must be per cpu, not global. Also you will fall
-v4.4-2.6.12-common-1.
2005-08-29 Keith Owens <[EMAIL PROTECTED]>
* kdb v4.4-2.6.13-common-1.
2005-08-24 Keith Owens <[EMAIL PROTECTED]>
* kdb v4.4-2.6.13-rc7-common-1.
2005-08-08 Keith Owens <[EMAIL PROTECTED]>
* kdb v4.4-2.6.13-rc6-common-1.
2005
-v4.4-2.6.12-common-1.
2005-08-29 Keith Owens [EMAIL PROTECTED]
* kdb v4.4-2.6.13-common-1.
2005-08-24 Keith Owens [EMAIL PROTECTED]
* kdb v4.4-2.6.13-rc7-common-1.
2005-08-08 Keith Owens [EMAIL PROTECTED]
* kdb v4.4-2.6.13-rc6-common-1.
2005-08-02 Keith Owens [EMAIL
On Wed, 24 Aug 2005 11:22:52 -0700,
Andrew Vasquez <[EMAIL PROTECTED]> wrote:
>On Wed, 24 Aug 2005, Keith Owens wrote:
>
>> 2.6.13-rc7 + kdb on ia64. The qla2xxx drivers are getting unaligned
>> accesses at startup.
>>
>> qla2300 :01:02.0: Found an ISP231
2.6.13-rc7 + kdb on ia64. The qla2xxx drivers are getting unaligned
accesses at startup.
qla2300 :01:02.0: Found an ISP2312, irq 66, iobase 0xc0080f30
qla2300 :01:02.0: Configuring PCI space...
PCI: slot :01:02.0 has incorrect PCI cache line size of 0 bytes, correcting
to
pcibios_bus_to_resource is exported on all architectures except ia64
and sparc. Add exports for the two missing architectures. Needed when
Yenta socket support is compiled as a module.
Signed-off-by: Keith Owens <[EMAIL PROTECTED]>
Index: linux/arch/ia64/pci
On Wed, 24 Aug 2005 11:22:52 -0700,
Andrew Vasquez [EMAIL PROTECTED] wrote:
On Wed, 24 Aug 2005, Keith Owens wrote:
2.6.13-rc7 + kdb on ia64. The qla2xxx drivers are getting unaligned
accesses at startup.
qla2300 :01:02.0: Found an ISP2312, irq 66, iobase 0xc0080f30
qla2300
pcibios_bus_to_resource is exported on all architectures except ia64
and sparc. Add exports for the two missing architectures. Needed when
Yenta socket support is compiled as a module.
Signed-off-by: Keith Owens [EMAIL PROTECTED]
Index: linux/arch/ia64/pci/pci.c
2.6.13-rc7 + kdb on ia64. The qla2xxx drivers are getting unaligned
accesses at startup.
qla2300 :01:02.0: Found an ISP2312, irq 66, iobase 0xc0080f30
qla2300 :01:02.0: Configuring PCI space...
PCI: slot :01:02.0 has incorrect PCI cache line size of 0 bytes, correcting
to
IA64 gets *** Warning: "pcibios_bus_to_resource"
[drivers/pcmcia/yenta_socket.ko] undefined!. Trivial fix, export
pcibios_bus_to_resource. Also export it on sparc64, which is the only
other architecture that defines pcibios_bus_to_resource but does not
export it.
Signed-off-by: K
FYI, the intermittent free after use in sysfs is still there in
2.6.13-rc6.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at
FYI, the intermittent free after use in sysfs is still there in
2.6.13-rc6.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at
IA64 gets *** Warning: pcibios_bus_to_resource
[drivers/pcmcia/yenta_socket.ko] undefined!. Trivial fix, export
pcibios_bus_to_resource. Also export it on sparc64, which is the only
other architecture that defines pcibios_bus_to_resource but does not
export it.
Signed-off-by: Keith Owens [EMAIL
On Tue, 9 Aug 2005 01:16:37 +0200,
Andi Kleen <[EMAIL PROTECTED]> wrote:
>On Tue, Aug 09, 2005 at 09:14:52AM +1000, Keith Owens wrote:
>> On Mon, 8 Aug 2005 21:28:50 +0200,
>> Andi Kleen <[EMAIL PROTECTED]> wrote:
>> >On Mon, Aug 08, 2005
On Mon, 8 Aug 2005 21:28:50 +0200,
Andi Kleen <[EMAIL PROTECTED]> wrote:
>On Mon, Aug 08, 2005 at 12:27:10PM -0700, Tom Rini wrote:
>> {
>> unsigned int icr = APIC_DM_FIXED | shortcut | vector | dest;
>> -if (vector == KDB_VECTOR)
>> +if (vector == NMI_VECTOR)
>> icr =
On Mon, 8 Aug 2005 10:44:04 -0700,
Andrew Morton <[EMAIL PROTECTED]> wrote:
>Sonny Rao <[EMAIL PROTECTED]> wrote:
>> Modules linked in: cpufreq_userspace cpufreq_stats freq_table
>> cpufreq_powersave
>> cpufreq_ondemand cpufreq_conservative ipv6 video thermal processor hotkey
>> fan co
>>
On Mon, 8 Aug 2005 10:44:04 -0700,
Andrew Morton [EMAIL PROTECTED] wrote:
Sonny Rao [EMAIL PROTECTED] wrote:
Modules linked in: cpufreq_userspace cpufreq_stats freq_table
cpufreq_powersave
cpufreq_ondemand cpufreq_conservative ipv6 video thermal processor hotkey
fan co
ntainer button
On Mon, 8 Aug 2005 21:28:50 +0200,
Andi Kleen [EMAIL PROTECTED] wrote:
On Mon, Aug 08, 2005 at 12:27:10PM -0700, Tom Rini wrote:
{
unsigned int icr = APIC_DM_FIXED | shortcut | vector | dest;
-if (vector == KDB_VECTOR)
+if (vector == NMI_VECTOR)
icr = (icr
On Tue, 9 Aug 2005 01:16:37 +0200,
Andi Kleen [EMAIL PROTECTED] wrote:
On Tue, Aug 09, 2005 at 09:14:52AM +1000, Keith Owens wrote:
On Mon, 8 Aug 2005 21:28:50 +0200,
Andi Kleen [EMAIL PROTECTED] wrote:
On Mon, Aug 08, 2005 at 12:27:10PM -0700, Tom Rini wrote:
{
unsigned int icr
On Thu, 4 Aug 2005 14:39:00 +0200,
Andi Kleen <[EMAIL PROTECTED]> wrote:
>> > That doesn't make much sense here. tasklet will only run when interrupts
>> > are enabled, and that is much later. You could move it to there.
>>
>> Where? Keep in mind it's really only x86_64 that isn't able to break
On Thu, 4 Aug 2005 14:39:00 +0200,
Andi Kleen [EMAIL PROTECTED] wrote:
That doesn't make much sense here. tasklet will only run when interrupts
are enabled, and that is much later. You could move it to there.
Where? Keep in mind it's really only x86_64 that isn't able to break
sooner.
On Wed, 03 Aug 2005 17:28:38 -0600,
"Christopher Friesen" <[EMAIL PROTECTED]> wrote:
>
>On i386, /proc//maps shows the following entry:
>
>e000-f000 ---p 00:00 0
>
>This page of memory is way up above TASK_SIZE (which is 0xc000), so
>how is it visible to userspace?
>
>Just
On Wed, 03 Aug 2005 17:28:38 -0600,
Christopher Friesen [EMAIL PROTECTED] wrote:
On i386, /proc/pid/maps shows the following entry:
e000-f000 ---p 00:00 0
This page of memory is way up above TASK_SIZE (which is 0xc000), so
how is it visible to userspace?
Just to
On Tue, 02 Aug 2005 18:12:27 -0700,
George Anzinger wrote:
>How about something like:
> if (current + THREAD_SIZE/sizeof(long) - (regs + sizeof(pt_regs)) >
> MAGIC)
current points to the current struct task, regs points to the kernel
stack. Those two data areas can be completely
On Tue, 2 Aug 2005 09:57:51 +0100 (BST),
vinay hegde <[EMAIL PROTECTED]> wrote:
>How to differentiate kernel threads from normal
>processes inside the Linux kernel code?
The Linux Kernel Debugger (ftp://oss.sgi.com/projects/kdb/download/v4.4)
distinguishes between idle tasks, sleeping system
On Tue, 2 Aug 2005 09:57:51 +0100 (BST),
vinay hegde [EMAIL PROTECTED] wrote:
How to differentiate kernel threads from normal
processes inside the Linux kernel code?
The Linux Kernel Debugger (ftp://oss.sgi.com/projects/kdb/download/v4.4)
distinguishes between idle tasks, sleeping system
On Tue, 02 Aug 2005 18:12:27 -0700,
George Anzinger george@mvista.com wrote:
How about something like:
if (current + THREAD_SIZE/sizeof(long) - (regs + sizeof(pt_regs))
MAGIC)
current points to the current struct task, regs points to the kernel
stack. Those two data areas can be
On Tue, 02 Aug 2005 13:05:50 +1000,
Keith Owens <[EMAIL PROTECTED]> wrote:
>The vcsnn value varies. I traced the dentry parent chain for the
>latest event. From bottom to top the d_name entries are
>
> dev, vcs16, vc, class, /.
>
>That makes no sense, why is dev a c
On Mon, 1 Aug 2005 12:03:21 -0700,
Andrew Morton <[EMAIL PROTECTED]> wrote:
>Keith Owens <[EMAIL PROTECTED]> wrote:
>>
>> On Sat, 30 Jul 2005 02:29:55 -0700,
>> Andrew Morton <[EMAIL PROTECTED]> wrote:
>> >Keith Owens <[EMAIL PROTECT
Another (different) manifestation of use after free in sysfs. It broke
on module_put(owner) in sysfs_release(). FWIW this ia64 build is
uni-processor, so there is a lot more context switching than normally
occurs on udev.
fill_kobj_path: path = '/class/vc/vcs2'
kobject_hotplug: /sbin/hotplug vc
On Sat, 30 Jul 2005 02:29:55 -0700,
Andrew Morton <[EMAIL PROTECTED]> wrote:
>Keith Owens <[EMAIL PROTECTED]> wrote:
>>
>> 2.6.13-rc4 + kdb, with lots of CONFIG_DEBUG options. There is an
>> intermittent use after free in class_device_attr_show. Reboot with no
On Sat, 30 Jul 2005 02:29:55 -0700,
Andrew Morton [EMAIL PROTECTED] wrote:
Keith Owens [EMAIL PROTECTED] wrote:
2.6.13-rc4 + kdb, with lots of CONFIG_DEBUG options. There is an
intermittent use after free in class_device_attr_show. Reboot with no
changes and the problem does not always
Another (different) manifestation of use after free in sysfs. It broke
on module_put(owner) in sysfs_release(). FWIW this ia64 build is
uni-processor, so there is a lot more context switching than normally
occurs on udev.
fill_kobj_path: path = '/class/vc/vcs2'
kobject_hotplug: /sbin/hotplug vc
On Mon, 1 Aug 2005 12:03:21 -0700,
Andrew Morton [EMAIL PROTECTED] wrote:
Keith Owens [EMAIL PROTECTED] wrote:
On Sat, 30 Jul 2005 02:29:55 -0700,
Andrew Morton [EMAIL PROTECTED] wrote:
Keith Owens [EMAIL PROTECTED] wrote:
2.6.13-rc4 + kdb, with lots of CONFIG_DEBUG options
On Tue, 02 Aug 2005 13:05:50 +1000,
Keith Owens [EMAIL PROTECTED] wrote:
The vcsnn value varies. I traced the dentry parent chain for the
latest event. From bottom to top the d_name entries are
dev, vcs16, vc, class, /.
That makes no sense, why is dev a child of vcs16? Raw data at the end
2.6.13-rc4 + kdb, with lots of CONFIG_DEBUG options. There is an
intermittent use after free in class_device_attr_show. Reboot with no
changes and the problem does not always recur.
Starting SSH daemon done
Starting sound driver
On Fri, 29 Jul 2005 13:55:23 -0700,
George Anzinger wrote:
> This patch adds a notify to the die_nmi notify that the system
> is about to be taken down. If the notify is handled with a
> NOTIFY_STOP return, the system is given a new lease on life.
>
> void die_nmi (struct
On Fri, 29 Jul 2005 00:22:43 -0700,
"Chen, Kenneth W" <[EMAIL PROTECTED]> wrote:
>On ia64, we have two kernel stacks, one for outgoing task, and one for
>incoming task. for outgoing task, we haven't called switch_to() yet.
>So the switch stack structure for 'current' will be allocated
On Fri, 29 Jul 2005 09:04:48 +0200,
Ingo Molnar <[EMAIL PROTECTED]> wrote:
>ok, how about the additional patch below? Does this do the trick on
>ia64? It makes complete sense on every architecture to prefetch from
>below the current kernel stack, in the expectation of the next task
>touching
On Fri, 29 Jul 2005 09:04:48 +0200,
Ingo Molnar [EMAIL PROTECTED] wrote:
ok, how about the additional patch below? Does this do the trick on
ia64? It makes complete sense on every architecture to prefetch from
below the current kernel stack, in the expectation of the next task
touching the
On Fri, 29 Jul 2005 00:22:43 -0700,
Chen, Kenneth W [EMAIL PROTECTED] wrote:
On ia64, we have two kernel stacks, one for outgoing task, and one for
incoming task. for outgoing task, we haven't called switch_to() yet.
So the switch stack structure for 'current' will be allocated immediately
below
On Fri, 29 Jul 2005 13:55:23 -0700,
George Anzinger george@mvista.com wrote:
This patch adds a notify to the die_nmi notify that the system
is about to be taken down. If the notify is handled with a
NOTIFY_STOP return, the system is given a new lease on life.
void die_nmi
On Thu, 28 Jul 2005 21:16:56 -0700,
George Anzinger wrote:
>Keith Owens wrote:
>> On Thu, 28 Jul 2005 13:31:58 -0700,
>> George Anzinger wrote:
>>
>>>I have been doing some work on kgdb to pull a few of it "fingers" out of
>>>various places in
On Thu, 28 Jul 2005 13:31:58 -0700,
George Anzinger wrote:
>I have been doing some work on kgdb to pull a few of it "fingers" out of
>various places in the kernel. This is the final location where we have
>a kgdb intercept not covered by a notify.
I like the idea, but the hook should be in
On Thu, 28 Jul 2005 09:41:18 +0200,
Ingo Molnar <[EMAIL PROTECTED]> wrote:
>
>* david mosberger <[EMAIL PROTECTED]> wrote:
>
>> Also, should this be called prefetch_stack() or perhaps even just
>> prefetch_task()? Not every architecture defines a switch_stack
>> structure.
>
>yeah. I'd too
On Thu, 28 Jul 2005 09:41:18 +0200,
Ingo Molnar [EMAIL PROTECTED] wrote:
* david mosberger [EMAIL PROTECTED] wrote:
Also, should this be called prefetch_stack() or perhaps even just
prefetch_task()? Not every architecture defines a switch_stack
structure.
yeah. I'd too suggest to call it
On Thu, 28 Jul 2005 13:31:58 -0700,
George Anzinger george@mvista.com wrote:
I have been doing some work on kgdb to pull a few of it fingers out of
various places in the kernel. This is the final location where we have
a kgdb intercept not covered by a notify.
I like the idea, but the hook
On Thu, 28 Jul 2005 21:16:56 -0700,
George Anzinger george@mvista.com wrote:
Keith Owens wrote:
On Thu, 28 Jul 2005 13:31:58 -0700,
George Anzinger george@mvista.com wrote:
I have been doing some work on kgdb to pull a few of it fingers out of
various places in the kernel
On Mon, 25 Jul 2005 15:01:19 -0700,
Andrew Morton <[EMAIL PROTECTED]> wrote:
>Keith Owens <[EMAIL PROTECTED]> wrote:
>>
>> 2.6.13-rc3 + kdb (which does not touch udev/hotplug) on IA64 (Altix).
>> gcc version 3.3.3 (SuSE Linux). Compiled with DEBUG_SLAB,
On Mon, 25 Jul 2005 15:01:19 -0700,
Andrew Morton [EMAIL PROTECTED] wrote:
Keith Owens [EMAIL PROTECTED] wrote:
2.6.13-rc3 + kdb (which does not touch udev/hotplug) on IA64 (Altix).
gcc version 3.3.3 (SuSE Linux). Compiled with DEBUG_SLAB,
DEBUG_PREEMPT, DEBUG_SPINLOCK
On Fri, 22 Jul 2005 19:46:00 +,
Sam Ravnborg <[EMAIL PROTECTED]> wrote:
>On Thu, Jul 21, 2005 at 11:06:21PM -0400, Chuck Ebbert wrote:
>>
>> I have this in my .config file for 2.6.13-rc3:
>>
>>
>> #
>> # Multimedia devices
>> #
>> # CONFIG_VIDEO_DEV is not set
>>
>> #
>> # Digital Video
1 - 100 of 1347 matches
Mail list logo
