lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CALCETrXEwHBdZyihN=rnraTKCWXNgwZ-9kZwB5gWSgA0u1FhAQ@mail.gmail.com>
Date:	Fri, 3 Jul 2015 09:23:05 -0700
From:	Andy Lutomirski <luto@...capital.net>
To:	David Herrmann <dh.herrmann@...il.com>
Cc:	Tom Gundersen <teg@...m.no>, Greg KH <gregkh@...uxfoundation.org>,
	Jiri Kosina <jkosina@...e.cz>,
	One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Daniel Mack <daniel@...que.org>, Arnd Bergmann <arnd@...db.de>,
	Djalal Harouni <tixxdz@...ndz.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [!GIT PULL] kdbus for 4.2

On Jul 3, 2015 1:43 AM, "David Herrmann" <dh.herrmann@...il.com> wrote:
>
> Hi
>
> On Fri, Jul 3, 2015 at 2:39 AM, Andy Lutomirski <luto@...capital.net> wrote:
> > Problem 1: Booting a kdbus-enabled kernel (CONFIG_KDBUS=y) causes gdm
> > to bail saying "oops, something went wrong" or whatever the useless
> > standard error message is.
> >
> > I can work around problem 1 by booting with kdbus=1, but that's not
> > okay.  Unless this is limited to just some narrow range of Rawhide
> > versions, I don't think the kernel gets to make changes that break
> > userspace like that.  Maybe this is a kernel issue, not a user issue,
> > in which case it's not a big deal as long as it gets fixed.
>
> You're saying booting with the same kernel but kdbus not compiled in works?
>

Yes, exactly.

The bad boot gets a couple warnings about dbus names getting lost or
something like that.

> > Problem 2: Running 'sudo mount /mnt/share' from a terminal hangs the
> > whole graphical session hard.  This is repeatable.  /mnt/share is
> > virtfs, but I doubt that matters.
>
> This is triggered by running through pam from outside the gfx-session
> but on a shared VT. It's not directly related to kdbus, though. It's
> fixed in systemd-git. As a workaround, you can remove pam_systemd from
> the sudo/su pam config.
>

I'll try on Monday.  Or maybe someone will build a new systemd on Rawhide :)

--Andy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ