linux-kernel - Re: [!GIT PULL] kdbus for 4.2

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] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 3 Jul 2015 10:43:21 +0200
From:	David Herrmann <dh.herrmann@...il.com>
To:	Andy Lutomirski <luto@...capital.net>
Cc:	Tom Gundersen <teg@...m.no>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Arnd Bergmann <arnd@...db.de>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>,
	Jiri Kosina <jkosina@...e.cz>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Daniel Mack <daniel@...que.org>,
	Djalal Harouni <tixxdz@...ndz.org>
Subject: Re: [!GIT PULL] kdbus for 4.2

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?

> 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.

Thanks
David
--
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/