All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Eugeniu Rosca <erosca@de.adit-jv.com>
Cc: dhowells@redhat.com
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	Alan Stern <stern@rowland.harvard.edu>,
	Mathias Nyman <mathias.nyman@linux.intel.com>,
	Kai-Heng Feng <kai.heng.feng@canonical.com>,
	Felipe Balbi <felipe.balbi@linux.intel.com>,
	Nicolas Boichat <drinkcat@chromium.org>,
	Mathias Payer <mathias.payer@nebelwelt.net>,
	Kento Kobayashi <Kento.A.Kobayashi@sony.com>,
	Hui Peng <benquike@gmail.com>,
	Raul E Rangel <rrangel@chromium.org>,
	Douglas Anderson <dianders@chromium.org>,
	Jan-Marek Glogowski <glogow@fbihome.de>, Bin Liu <b-liu@ti.com>,
	Colin Ian King <colin.king@canonical.com>,
	Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
	Jon Flatley <jflat@chromium.org>,
	Mathieu Malaterre <malat@debian.org>,
	Spyridon Papageorgiou <spapageorgiou@de.adit-jv.com>,
	Joshua Frkuska <joshua_frkuska@mentor.com>,
	"George G . Davis" <george_davis@mentor.com>,
	yuichi.kusakabe@denso-ten.com, yohhei.fukui@denso-ten.com,
	natsumi.kamei@denso-ten.com, yasano@jp.adit-jv.com,
	sliu@de.adit-jv.com, Eugeniu Rosca <roscaeugeniu@gmail.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] usb: hub: report failure to enumerate uevent to userspace
Date: Wed, 05 Jun 2019 22:19:43 +0100	[thread overview]
Message-ID: <6439.1559769583@warthog.procyon.org.uk> (raw)
In-Reply-To: <20190605165530.GA15790@vmlxhi-102.adit-jv.com>

Eugeniu Rosca <erosca@de.adit-jv.com> wrote:

>  - Looking at commit [4], it seems that the new "notifier" interface/api
>    forces userspace applications to link against -lkeyutils [5].

No.  The keyctl(2) syscall is implemented in -lkeyutils library, and not in
-lc.  That's all.  If you want to call KEYCTL_NOTIFY to watch a key or
keyring, you need it; not otherwise.

>    Assuming the latter is designed for ("Kernel key management") [6],
>    it may look like the keyutils library is being abused to handle
>    the "USB (or really any hardware events)". Do you really plan to
>    extend the scope of the library to handle these new tasks?

No.

That said, it's probably worth providing some userspace library to wrap the
ring management.

David

  parent reply	other threads:[~2019-06-05 21:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-05  9:05 [PATCH] usb: hub: report failure to enumerate uevent to userspace Eugeniu Rosca
2019-06-05 10:03 ` Greg Kroah-Hartman
2019-06-05 16:55   ` Eugeniu Rosca
2019-06-05 17:48     ` Greg Kroah-Hartman
2019-06-05 21:19   ` David Howells [this message]
2019-06-05 21:22   ` David Howells

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=6439.1559769583@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=erosca@de.adit-jv.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.