From: Jes Sorensen <jes@linuxcare.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Re: Fault 26?
Date: Fri, 08 Dec 2000 17:53:36 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205818@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205793@msgid-missing>
>>>>> "Dan" = Dan Pop <Dan.Pop@cern.ch> writes:
Dan> On Wed, 6 Dec 2000, Bill Nottingham wrote:
>> David Mosberger (davidm@hpl.hp.com) said: > Bill> What is fault
>> type 26? I'm getting a few of these recently. > > It's the "NaT
>> consumption fault". Either buggy code is trying to eat > a NaT
>> value or something else goes wrong and a NaT value is created >
>> when it shouldn't be.
>>
>> It's happening in strcpy(), of all places, with two seemingly valid
>> arguments.
Dan> Here's a patch that should fix it. The bug was in a recovery
Dan> code that was highly unlikely to be ever executed, hence it
Dan> passed unnoticed for so long :-)
Great
I have applied this to my tree and asked Ulrich to apply it to the
official tree.
Jes
prev parent reply other threads:[~2000-12-08 17:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-05 22:23 [Linux-ia64] Re: Fault 26? Bill Nottingham
2000-12-06 22:18 ` Bill Nottingham
2000-12-07 4:32 ` Dan Pop
2000-12-07 4:41 ` David Mosberger
2000-12-08 17:53 ` Jes Sorensen [this message]
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-105590678205818@msgid-missing \
--to=jes@linuxcare.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