From: Dave Jones <davej@redhat.com>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: trinity@vger.kernel.org
Subject: Re: trinity cores in watchdog while syslog'ing
Date: Wed, 6 Aug 2014 14:28:04 -0400 [thread overview]
Message-ID: <20140806182804.GB4605@redhat.com> (raw)
In-Reply-To: <53E270FB.8040900@gmx.de>
On Wed, Aug 06, 2014 at 08:16:27PM +0200, Toralf Förster wrote:
> Just FWIW :
>
> Fuzzying a 32 bit Gentoo Linux let the trinity process in side the UML guest sometimes core dump with this back trace:
>
> Core was generated by `trinity -C 4 -N 100000 -x mremap -q'.
> Program terminated with signal 11, Segmentation fault.
> #0 __GI__IO_fflush (fp=0x8154200) at iofflush.c:40
> 40 iofflush.c: No such file or directory.
> (gdb) bt
> #0 __GI__IO_fflush (fp=0x8154200) at iofflush.c:40
> #1 0x080582c3 in synclogs () at log.c:163
> #2 0x0805e93d in watchdog () at watchdog.c:363
> #3 init_watchdog () at watchdog.c:430
> #4 0x080538d9 in main (argc=8, argv=0xbfc8fd94) at trinity.c:132
> (gdb) quit
ugh, when I switched the log file creation to happen from within
the child, I forgot to take care of this function.
I'm surprised it's taken this long for anyone to notice, as it can't
possibly work.
I think I'm just going to tear that whole thing out, as syncing
from watchdog context just isn't going to be possible.
Dave
next prev parent reply other threads:[~2014-08-06 18:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-06 18:16 trinity cores in watchdog while syslog'ing Toralf Förster
2014-08-06 18:28 ` Dave Jones [this message]
2014-08-06 19:14 ` Toralf Förster
2014-08-06 20:05 ` Dave Jones
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=20140806182804.GB4605@redhat.com \
--to=davej@redhat.com \
--cc=toralf.foerster@gmx.de \
--cc=trinity@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;
as well as URLs for NNTP newsgroup(s).