linux-kernel - Re: [RFC PATCH] kdbus: move all kdbus headers to include/linux/kdbus

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:	Wed, 25 Mar 2015 17:07:45 +0100 (CET)
From:	Paul Osmialowski <p.osmialowsk@...sung.com>
To:	David Herrmann <dh.herrmann@...il.com>
Cc:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Daniel Mack <daniel@...que.org>,
	Djalal Harouni <tixxdz@...ndz.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Lukasz Skalski <l.skalski@...sung.com>,
	Paul Osmialowski <p.osmialowsk@...sung.com>
Subject: Re: [RFC PATCH] kdbus: move all kdbus headers to include/linux/kdbus

Hi,

First of all, I'm sorry for this no-subject covering letter. Accidents 
never happen only in a perfect world.

On Wed, 25 Mar 2015, David Herrmann wrote:

>
> I'd prefer if we only move the required structure definitions into a
> separate header. There is no reason to export all internal entry
> points.
>

You're right, this would definitely look nicer.

>
> Anyway, this is a technicality that actually depends on the
> implemented LSM hooks. So I'd prefer if we discuss that in combination
> with the actual LSM patches. I'm not entirely sure which parts are
> needed. For testing-purposes, we can always use -I./ipc/kdbus/, right?
>

Yes we can, which makes whole this patch a bit premature.

However, we can't predict whether someone may want to use kdbus headers 
for any other purpose. As for now, I don't see immediate need for this 
apart from implementing LSM callbacks.

Thanks,
Paul
--
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/