From: Ben Woodard <woodard@redhat.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch] 0/5 2.4.25-pre7 mca.c cleanup
Date: Wed, 04 Feb 2004 02:45:58 +0000 [thread overview]
Message-ID: <1075862758.11543.130.camel@xenophanes> (raw)
In-Reply-To: <6503.1075705201@kao2.melbourne.sgi.com>
On Tue, 2004-02-03 at 17:19, Ben Woodard wrote:
> The changes in salinfo_decode.c fix a problem where the salinfo_decode
> daemon crashes when it receives the second error since stdout and stderr
> are already closed causing the freopen to fail.
>
Oops I forgot to explain why this is important. With this bug in the
salinfo_decode, the daemon exits when it tries to open the decoded file
for the 2nd cpe it receives. Thus the computer stays up since the
salinfo_decode daemon is not running.
Since we know that the daemon has already seen the event, fetched the
data, and written the raw version of the error. The only interaction
that it has with the salinfo /proc file system code is the handling of
the write to clear the error. This is leading me to believe that the
race is between the salinfo write routine and the cpe handler over in
mca.c. I just haven't spotted the problem yet. (though I could be blind
or off target.)
-ben
next prev parent reply other threads:[~2004-02-04 2:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-02 7:00 [patch] 0/5 2.4.25-pre7 mca.c cleanup Keith Owens
2004-02-03 0:36 ` Ben Woodard
2004-02-03 1:27 ` Keith Owens
2004-02-04 1:19 ` Ben Woodard
2004-02-04 2:45 ` Ben Woodard [this message]
2004-02-04 7:18 ` Hidetoshi Seto
2004-02-04 20:59 ` Keith Owens
2004-02-04 23:27 ` Bjorn Helgaas
2004-02-04 23:42 ` 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=1075862758.11543.130.camel@xenophanes \
--to=woodard@redhat.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