linux-kernel - Re: [GIT PULL] kdbus for 4.1-rc1

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]

Message-ID: <alpine.DEB.2.02.1504290935140.25285@nftneq.ynat.uz>
Date:	Wed, 29 Apr 2015 09:36:46 -0700 (PDT)
From:	David Lang <david@...g.hm>
To:	Martin Steigerwald <martin@...htvoll.de>
cc:	Harald Hoyer <harald@...hat.com>, John Stoffel <john@...ffel.org>,
	Havoc Pennington <hp@...ox.com>,
	"Theodore Ts'o" <tytso@....edu>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andy Lutomirski <luto@...capital.net>,
	Lukasz Skalski <l.skalski@...sung.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.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>,
	Tom Gundersen <teg@...m.no>, Jiri Kosina <jkosina@...e.cz>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Daniel Mack <daniel@...que.org>,
	David Herrmann <dh.herrmann@...il.com>,
	Djalal Harouni <tixxdz@...ndz.org>
Subject: Re: [GIT PULL] kdbus for 4.1-rc1

On Wed, 29 Apr 2015, Martin Steigerwald wrote:

> Am Mittwoch, 29. April 2015, 14:47:53 schrieb Harald Hoyer:
>> We really don't want the IPC mechanism to be in a flux state. All tools
>> have to fallback to a non-standard mechanism in that case.
>>
>> If I have to pull in a dbus daemon in the initramfs, we still have the
>> chicken and egg problem for PID 1 talking to the logging daemon and
>> starting dbus.
>> systemd cannot talk to journald via dbus unless dbus-daemon is started,
>> dbus cannot log anything on startup, if journald is not running, etc...
>
> Do I get this right that it is basically a userspace *design* decision
> that you use as a reason to have kdbus inside the kernel?
>
> Is it really necessary to use DBUS for talking to journald? And does it
> really matter that much if any message before starting up dbus do not
> appear in the log? /proc/kmsg is a ring buffer, it can still be copied over
> later.

I've been getting the early boot messages in my logs for decades (assuming the 
system doesn't fail before the syslog daemon is started). It sometimes has 
required setting a larger than default ringbuffer in the kernel, but that's easy 
enough to do.

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