From: David Woodhouse <dwmw2@infradead.org>
To: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
Cc: linux-kernel@vger.kernel.org, jmerkey@timpanogas.org
Subject: Re: filp_open() in 2.2.19 causes memory corruption
Date: Fri, 27 Apr 2001 12:50:45 +0100 [thread overview]
Message-ID: <5157.988372245@redhat.com> (raw)
In-Reply-To: <20010425173210.A13124@vger.timpanogas.org>
In-Reply-To: <20010425173210.A13124@vger.timpanogas.org> <20010423163757.D1131@vger.timpanogas.org> <20010423163248.B1131@vger.timpanogas.org> <001d01c0cc33$7e62daa0$5517fea9@local> <3942.988063428@redhat.com> <20010423163248.B1131@vger.timpanogas.org> <4750.988065680@redhat.com> <20010423163757.D1131@vger.timpanogas.org> <4855.988065927@redhat.com> <20010423163954.A1237@vger.timpanogas.org> <4897.988066047@redhat.com>
jmerkey@vger.timpanogas.org said:
> I've gotten to the bottom of this problem, and you are correct that
> klog is trashing the messages file for the oops.
Oh dear. That's quite a serious bug in klogd. It should never destroy the
original information, _especially_ if the System.map it's looking at
blatantly doesn't match /proc/ksyms.
Have you reported it to your distribution vendor yet?
--
dwmw2
next prev parent reply other threads:[~2001-04-27 11:51 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
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 [this message]
-- 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=5157.988372245@redhat.com \
--to=dwmw2@infradead.org \
--cc=jmerkey@timpanogas.org \
--cc=jmerkey@vger.timpanogas.org \
--cc=linux-kernel@vger.kernel.org \
/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