From: Dave Jones <davej@redhat.com>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: trinity@vger.kernel.org
Subject: Re: BUG!: unreachable!
Date: Thu, 2 Oct 2014 11:48:25 -0400 [thread overview]
Message-ID: <20141002154825.GA19347@redhat.com> (raw)
In-Reply-To: <542C3D04.4030503@gmx.de>
On Wed, Oct 01, 2014 at 07:42:28PM +0200, Toralf Förster wrote:
> JJust FWIW with current git tree of trinity I run into this :
>
> [child2:30294] <timed out>
> [child2:30294] <timed out>
> BUG!: unreachable!
>
> BUG!: 9
> BUG!: [30306] generate-args.c:fill_arg:367
> [child3:30301] <timed out>
> [child3:30301] <timed out>
> [child3:30316] <timed out>
> BUG!: unreachable!
>
> BUG!: 9
> BUG!: [30316] generate-args.c:fill_arg:367
> [child0:30306] trinity(show_backtrace+0x32) [0x80551f2]
>
> but I must admit this around the same time where the oom killer killed few tasks within the 32 bit KVM machine whre trintiy was fuzzying the kernel.
This is really bad, something has scribbled over trinity's syscall
definitions, and the type of the argument is garbage.
Not enough info to really say what the cause of that was,
whether it was a trinity bug, or uml bug.
Hm, I wonder if it's worth mprotect(PROT_READ)'ing trinity's
core structures that become read-only after setup.
Dave
prev parent reply other threads:[~2014-10-02 15:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 17:42 BUG!: unreachable! Toralf Förster
2014-10-02 15:48 ` Dave Jones [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=20141002154825.GA19347@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).