From: Valdis.Kletnieks@vt.edu
To: Eric Paris <eparis@redhat.com>
Cc: Paul Moore <paul@paul-moore.com>,
linux-kernel@vger.kernel.org, selinux@tycho.nsa.gov,
linux-audit@redhat.com, rgb@redhat.com
Subject: Re: linux-next 20141216 BUG: sleeping function called from invalid context at mm/slab.c:2849
Date: Thu, 18 Dec 2014 14:21:13 -0500 [thread overview]
Message-ID: <8832.1418930473@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Thu, 18 Dec 2014 11:50:20 -0500." <1418921420.5162.19.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 1017 bytes --]
On Thu, 18 Dec 2014 11:50:20 -0500, Eric Paris said:
> On Thu, 2014-12-18 at 11:45 -0500, Valdis.Kletnieks@vt.edu wrote:
> > On Tue, 16 Dec 2014 20:09:54 -0500, Valdis Kletnieks said:
> >
> > > Spotted these two while booting single-user on 20141216. 20141208
> > > doesn't throw these, so it's something in the last week or so..
> >
> > Gaah! Turns out that 20141208 *is* susceptible - it had been booting
> > just fine for several days, but it went around the bend, apparently due
> > to a userspace or initrd change.
>
> $5 says you updated systemd?
Actually, yeah. yum.log says:
Dec 12 14:08:09 Updated: systemd-218-1.fc22.x86_64
and things started going downhill that evening. Damned if I know what 218
was doing to cause the issues. (Other RPM update that looked vaguely
related was for selinux-policy, but again, damned if I know what a policy
file could contain that would change the behavior...)
Is it worth backing it to -217, or do we have a handle on the issue and
systemd is just the messenger?
[-- Attachment #2: Type: application/pgp-signature, Size: 848 bytes --]
next prev parent reply other threads:[~2014-12-18 19:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2966.1418778594@turing-police.cc.vt.edu>
2014-12-17 1:21 ` linux-next 20141216 BUG: sleeping function called from invalid context at mm/slab.c:2849 Eric Paris
2014-12-17 22:44 ` Richard Guy Briggs
[not found] ` <5444.1418921116@turing-police.cc.vt.edu>
2014-12-18 16:50 ` Eric Paris
2014-12-18 17:46 ` Richard Guy Briggs
2014-12-18 17:50 ` Eric Paris
2014-12-18 18:44 ` Richard Guy Briggs
2014-12-18 19:04 ` Eric Paris
2014-12-18 20:03 ` Paul Moore
2014-12-18 19:21 ` Valdis.Kletnieks [this message]
2014-12-18 19:24 ` Richard Guy Briggs
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=8832.1418930473@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=eparis@redhat.com \
--cc=linux-audit@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=rgb@redhat.com \
--cc=selinux@tycho.nsa.gov \
/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