Linux-USB Archive on
 help / color / Atom feed
From: Eugeniu Rosca <>
To: David Howells <>
Cc: Eugeniu Rosca <>,
	Spyridon Papageorgiou <>,
	Greg Kroah-Hartman <>,
	Eugeniu Rosca <>
Subject: Re: Do you have a sink for USB notifications?
Date: Thu, 16 Jan 2020 19:01:01 +0100
Message-ID: <> (raw)
In-Reply-To: <>

Hi David,

On Thu, Jan 16, 2020 at 02:16:41PM +0000, David Howells wrote:
> Hi Eugeniu, Spyridon,
> Greg pointed me at your patch:

I remember this thread.

> Do you have a consumer program for USB notification events? 

As you might expect, looking at the above patch, we are using
'udevadm monitor' in the development environment. The end user is
making sense of the notifications either via udev daemon or via
a custom libudev-linked application.

> I'm would like to
> get my general notification queue patches upstream in this merge window, but
> it appears that Linus would like there to be userspace consumers first.
> My latest patch set is here:
> This provides access to keyring, usb and block device notifications.

It's great to see new and creative solutions being proposed in upstream,
especially if those attempt improving system reliability, robustness and
help standardizing the interfaces.

However, to be honest, I am concerned of below:
 - The amount of code [*] I have to compile/link to enable the feature
   (as opposed to ~15 lines of *.c code in the aforementioned patch)
 - No active users
 - No readily available userspace applications to handle the events
 - No complaints from the customers w.r.t. udevd/libudev (no secret, 
   this is what most of the times funds our work and drives the
   industry forward)

I am still ready to offer any help, if needed. TIA!

> Thanks,
> David

[*] git diff --shortstat v5.5-rc3..linux-fs/notifications-pipe-core
    63 files changed, 2505 insertions(+), 106 deletions(-)

Best Regards,

      reply index

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-16 14:16 David Howells
2020-01-16 18:01 ` Eugeniu Rosca [this message]

Reply instructions:

You may reply publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-USB Archive on

Archives are clonable:
	git clone --mirror linux-usb/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-usb linux-usb/ \
	public-inbox-index linux-usb

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone