From: Steven Barnhart <sbarn03@softhome.net>
To: Daniel Ritz <daniel.ritz@gmx.ch>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.5.54 - Oops] CPUFreq [Was: Re: [2.5.54] OOPS: unable to
Date: 05 Jan 2003 16:16:19 -0500 [thread overview]
Message-ID: <1041801384.6490.4.camel@sbarn.net> (raw)
In-Reply-To: <20030105195445.AD456437D@ritz.dnsalias.org>
On Sun, 2003-01-05 at 13:54, Daniel Ritz wrote:
> looking at the oops it seems that it's the bufferoverflow in kallsyms_lookup.
> you are using 2.5.54 vanilla, aren't you.
> i already posted the patch for that which linus included. try to download the bk1
> snapshot (or higher) or just apply the following patch....
>
> beep
> -daniel
Thanks daniel, just did a pull..will be in touch.
Steven
sbarn03@softhome.net
GnuPG Fingerprint: 9357 F403 B0A1 E18D 86D5 2230 BB92 6D64 D516 0A94
parent reply other threads:[~2003-01-05 21:07 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20030105195445.AD456437D@ritz.dnsalias.org>]
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=1041801384.6490.4.camel@sbarn.net \
--to=sbarn03@softhome.net \
--cc=daniel.ritz@gmx.ch \
--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