Messages in this thread | | | Date | Mon, 23 Apr 2001 16:32:48 -0600 | From | "Jeff V. Merkey" <> | Subject | Re: filp_open() in 2.2.19 causes memory corruption |
| |
On Mon, Apr 23, 2001 at 11:03:48PM +0100, David Woodhouse wrote: > > manfred@colorfullife.com said: > > Are you sure the trace is decoded correctly? > > > > CPU: 0 > > > EIP: 0010:[sys_mremap+31/884] > > Probably not. It looks like it was munged by klogd. Some distributions are > still shipping with klogd configured to destroy the original information on > the way to the log, without even making it do a sanity check that the > System.map it's using actually matches the current kernel. > > Jeff, please disable the broken klogd symbol munging and reproduce it, > running the oops through ksymoops manually. Ksymoops should have built-in > sanity checks on the System.map it tries to use. > > Also, please make sure you report this as a serious bug with the vendor of > whatever distribution you're running on this box. >
David,
I will comply and repost the oops.
Jeff
> -- > dwmw2 > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |