> > 2005/11/30, Steven Rostedt <[email protected]>: > > > > The oops happened at address a01b50eb. Could you go into the compiled > > directory run gdb on vmlinux and type li *0xa01b50eb and show what you > > get. It turned out to be a bug in the vserver patches. Sent to maintainer. As it's not a mainline issue, I'm not bothering you any more. Thanks for debugging tips :) Best regards, Grzegorz Nosek - 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 http://www.tux.org/lkml/
- References:
- [PATCH] race condition in procfs
- From: Grzegorz Nosek <[email protected]>
- Re: [PATCH] race condition in procfs
- From: Grzegorz Nosek <[email protected]>
- Re: [PATCH] race condition in procfs
- From: Steven Rostedt <[email protected]>
- Re: [PATCH] race condition in procfs
- From: Grzegorz Nosek <[email protected]>
- Re: [PATCH] race condition in procfs
- From: Steven Rostedt <[email protected]>
- Re: [PATCH] race condition in procfs
- From: Grzegorz Nosek <[email protected]>
- Re: [PATCH] race condition in procfs
- From: Steven Rostedt <[email protected]>
- Re: [PATCH] race condition in procfs
- From: Grzegorz Nosek <[email protected]>
- Re: [PATCH] race condition in procfs
- From: Steven Rostedt <[email protected]>
- Re: [PATCH] race condition in procfs
- From: Grzegorz Nosek <[email protected]>
- [PATCH] race condition in procfs
- Prev by Date: Re: Fw: crash on x86_64 - mm related?
- Next by Date: Suppress your appetite and feel full and satisfied all day long
- Previous by thread: Re: [PATCH] race condition in procfs
- Next by thread: [PATCH] shrinks dentry struct
- Index(es):
 |