From: David Woodhouse <dwmw2@infradead.org>
To: "Manfred Spraul" <manfred@colorfullife.com>
Cc: jmerkey@vger.timpanogas.org, linux-kernel@vger.kernel.org
Subject: Re: filp_open() in 2.2.19 causes memory corruption
Date: Mon, 23 Apr 2001 23:03:48 +0100 [thread overview]
Message-ID: <3942.988063428@redhat.com> (raw)
In-Reply-To: <001d01c0cc33$7e62daa0$5517fea9@local>
In-Reply-To: <001d01c0cc33$7e62daa0$5517fea9@local>
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.
--
dwmw2
next prev parent reply other threads:[~2001-04-23 22:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-23 20:24 filp_open() in 2.2.19 causes memory corruption Manfred Spraul
2001-04-23 20:44 ` Jeff V. Merkey
2001-04-23 22:03 ` David Woodhouse [this message]
2001-04-23 22:32 ` Jeff V. Merkey
[not found] ` <4750.988065680@redhat.com>
[not found] ` <20010423163757.D1131@vger.timpanogas.org>
[not found] ` <4855.988065927@redhat.com>
[not found] ` <20010423163954.A1237@vger.timpanogas.org>
[not found] ` <4897.988066047@redhat.com>
2001-04-25 23:32 ` Jeff V. Merkey
2001-04-27 11:50 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2001-04-23 18:04 Jeff V. Merkey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3942.988063428@redhat.com \
--to=dwmw2@infradead.org \
--cc=jmerkey@vger.timpanogas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox