From: Russell Coker <russell@coker.com.au>
To: Nicolas Iooss <nicolas.iooss@m4x.org>
Cc: SElinux list <selinux@vger.kernel.org>,
Laurent Bigonville <bigon@debian.org>
Subject: Re: semodule -i and load_policy coredumps on version 3.0 - not latest GIT
Date: Thu, 16 Apr 2020 03:17:25 +1000 [thread overview]
Message-ID: <3781162.572I9EPuCd@liv> (raw)
In-Reply-To: <CAJfZ7==9L2PZkbBO22=RapRKvdiZQ1Fj7jgEhNSUcZ1hTDyKPA@mail.gmail.com>
On Wednesday, 15 April 2020 3:27:38 AM AEST Nicolas Iooss wrote:
> This looks a pretty difficult issue. The facts that it is not easily
> reproducible and that the stack trace changes even though the 2
> modules you are testing do not are interesting. They imply that there
> is some randomness involved. As far as I remember the code I've read
I'm still debugging this. My first belief that the bug was fixed in the latest
git seems incorrect. I've now got a collection of valgrind logs from libsepol
from git revision 5447c8490b318ef64c61eb6022baddca69233733 (latest as of
yesterday afternoon). I presume that the valgrind logs of "Conditional jump
or move depends on uninitialised value(s)" corresponds to a SEGV when not
running valgrind but haven't proven that yet.
I have not yet worked out how to reproduce the bug on another system.
Nickolas, thanks for all your suggestions I will go back to them once I have
more test results.
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
next prev parent reply other threads:[~2020-04-15 17:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 0:29 semodule -i and load_policy coredumps on version 3.0 - not latest GIT Russell Coker
2020-04-14 17:27 ` Nicolas Iooss
2020-04-15 17:17 ` Russell Coker [this message]
2020-04-21 4:01 ` Russell Coker
2020-04-22 10:49 ` Russell Coker
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=3781162.572I9EPuCd@liv \
--to=russell@coker.com.au \
--cc=bigon@debian.org \
--cc=nicolas.iooss@m4x.org \
--cc=selinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.