From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] insmod bug causes kernel unwind failures for module text
Date: Tue, 30 Jul 2002 00:03:32 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905849@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905831@msgid-missing>
>>>>> On Thu, 25 Jul 2002 13:38:27 -0400, Dave Anderson <anderson@redhat.com> said:
Dave> There is a bug in the initialization of the unw_table_entry
Dave> structures for all kernel modules, such that any unwind
Dave> operation that comes upon a kernel module text address will
Dave> fail to find its associated unwind info data in the
Dave> build_script() routine. (Actually it won't be able to
Dave> determine what module it belongs to.)
Has this been resolved?
I don't recall seeing any followups.
--david
next prev parent reply other threads:[~2002-07-30 0:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-25 17:38 [Linux-ia64] insmod bug causes kernel unwind failures for module text Dave Anderson
2002-07-30 0:03 ` David Mosberger [this message]
2002-07-30 1:43 ` Keith Owens
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=marc-linux-ia64-105590701905849@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@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