From: Paul Moore <paul@paul-moore.com>
To: Ondrej Mosnacek <omosnace@redhat.com>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
Jeff Vander Stoep <jeffv@google.com>,
Eric Paris <eparis@parisplace.org>, Jann Horn <jannh@google.com>,
Kees Cook <keescook@chromium.org>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
"Paul E. McKenney" <paulmck@kernel.org>,
SElinux list <selinux@vger.kernel.org>,
syzkaller-bugs@googlegroups.com,
syzbot <syzbot+61cba5033e2072d61806@syzkaller.appspotmail.com>
Subject: Re: possible deadlock in sidtab_sid2str_put
Date: Tue, 28 Jan 2020 12:29:19 -0500 [thread overview]
Message-ID: <CAHC9VhTHUjdYujta-bOd=AG+XLic6rAZbp2sEpC86vVnpkmBVA@mail.gmail.com> (raw)
In-Reply-To: <CAFqZXNv77JHa-6BPzEomZaj2uJqGrBRXrK68cTL0N0--Kz_PkA@mail.gmail.com>
On Tue, Jan 28, 2020 at 11:31 AM Ondrej Mosnacek <omosnace@redhat.com> wrote:
> ... the current rawhide 5.5.0-1 kernel seems to have some bug
> that prevents it from booting on anything with more than one core.
> I'll see if I can work around it somehow...
I'm not sure how you are building your kernels, but gcc v10 is causing
a lot of problems, I would suggest compiling with an earlier gcc for
the near future until things get sorted (I'm doing the kernel-secnext
builds on stable Fedora, not Rawhide, for now).
--
paul moore
www.paul-moore.com
next prev parent reply other threads:[~2020-01-28 17:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 4:27 possible deadlock in sidtab_sid2str_put syzbot
2020-01-28 12:50 ` syzbot
2020-01-28 13:39 ` Paul Moore
2020-01-28 13:45 ` Stephen Smalley
2020-01-28 14:26 ` Ondrej Mosnacek
2020-01-28 15:45 ` Paul Moore
2020-01-28 16:30 ` Ondrej Mosnacek
2020-01-28 17:29 ` Paul Moore [this message]
2020-02-03 8:46 ` Ondrej Mosnacek
2020-01-28 13:51 ` Ondrej Mosnacek
2020-01-28 15:28 ` syzbot
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='CAHC9VhTHUjdYujta-bOd=AG+XLic6rAZbp2sEpC86vVnpkmBVA@mail.gmail.com' \
--to=paul@paul-moore.com \
--cc=eparis@parisplace.org \
--cc=jannh@google.com \
--cc=jeffv@google.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=omosnace@redhat.com \
--cc=paulmck@kernel.org \
--cc=sds@tycho.nsa.gov \
--cc=selinux@vger.kernel.org \
--cc=syzbot+61cba5033e2072d61806@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/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.