All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: David Howells <dhowells@redhat.com>
Cc: viro@zeniv.linux.org.uk, Casey Schaufler <casey@schaufler-ca.com>,
	Stephen Smalley <sds@tycho.nsa.gov>,
	nicolas.dichtel@6wind.com, raven@themaw.net,
	Christian Brauner <christian@brauner.io>,
	keyrings@vger.kernel.org, linux-usb@vger.kernel.org,
	linux-security-module@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, linux-api@vger.kernel.org,
	linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6/9] Add a general, global device notification watch list [ver #5]
Date: Fri, 05 Jul 2019 05:17:33 +0000	[thread overview]
Message-ID: <20190705051733.GA15821@kroah.com> (raw)
In-Reply-To: <10295.1562256260@warthog.procyon.org.uk>

On Thu, Jul 04, 2019 at 05:04:20PM +0100, David Howells wrote:
> Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> 
> > Don't we need a manpage and a kselftest for it?
> 
> I've got part of a manpage, but it needs more work.
> 
> How do you do a kselftest for this when it does nothing unless hardware events
> happen?

Hm, good point, but there should be some way to test this to verify it
works.  Maybe for the other types of events?

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: David Howells <dhowells@redhat.com>
Cc: viro@zeniv.linux.org.uk, Casey Schaufler <casey@schaufler-ca.com>,
	Stephen Smalley <sds@tycho.nsa.gov>,
	nicolas.dichtel@6wind.com, raven@themaw.net,
	Christian Brauner <christian@brauner.io>,
	keyrings@vger.kernel.org, linux-usb@vger.kernel.org,
	linux-security-module@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, linux-api@vger.kernel.org,
	linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6/9] Add a general, global device notification watch list [ver #5]
Date: Fri, 5 Jul 2019 07:17:33 +0200	[thread overview]
Message-ID: <20190705051733.GA15821@kroah.com> (raw)
In-Reply-To: <10295.1562256260@warthog.procyon.org.uk>

On Thu, Jul 04, 2019 at 05:04:20PM +0100, David Howells wrote:
> Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> 
> > Don't we need a manpage and a kselftest for it?
> 
> I've got part of a manpage, but it needs more work.
> 
> How do you do a kselftest for this when it does nothing unless hardware events
> happen?

Hm, good point, but there should be some way to test this to verify it
works.  Maybe for the other types of events?

thanks,

greg k-h

  reply	other threads:[~2019-07-05  5:17 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-28 15:48 [PATCH 0/9] Keyrings, Block and USB notifications [ver #5] David Howells
2019-06-28 15:48 ` David Howells
2019-06-28 15:48 ` David Howells
2019-06-28 15:48 ` [PATCH 1/9] uapi: General notification ring definitions " David Howells
2019-06-28 15:48   ` David Howells
2019-06-28 15:48   ` David Howells
2019-07-03 17:08   ` Greg Kroah-Hartman
2019-07-03 17:08     ` Greg Kroah-Hartman
2019-06-28 15:48 ` [PATCH 2/9] security: Add hooks to rule on setting a watch " David Howells
2019-06-28 15:48   ` David Howells
2019-06-28 15:48   ` David Howells
2019-07-08 18:46   ` Stephen Smalley
2019-07-08 18:46     ` Stephen Smalley
2019-06-28 15:49 ` [PATCH 3/9] security: Add a hook for the point of notification insertion " David Howells
2019-06-28 15:49   ` David Howells
2019-06-28 15:49   ` David Howells
2019-07-08 19:13   ` Stephen Smalley
2019-07-08 19:13     ` Stephen Smalley
2019-06-28 15:49 ` [PATCH 4/9] General notification queue with user mmap()'able ring buffer " David Howells
2019-06-28 15:49   ` David Howells
2019-06-28 15:49   ` David Howells
2019-07-03 17:11   ` Greg Kroah-Hartman
2019-07-03 17:11     ` Greg Kroah-Hartman
2019-06-28 15:49 ` [PATCH 5/9] keys: Add a notification facility " David Howells
2019-06-28 15:49   ` David Howells
2019-06-28 15:49   ` David Howells
2019-06-28 15:49 ` [PATCH 6/9] Add a general, global device notification watch list " David Howells
2019-06-28 15:49   ` David Howells
2019-06-28 15:49   ` David Howells
2019-07-03 17:16   ` Greg Kroah-Hartman
2019-07-03 17:16     ` Greg Kroah-Hartman
2019-07-03 19:08   ` Greg Kroah-Hartman
2019-07-03 19:08     ` Greg Kroah-Hartman
2019-07-04 16:04     ` David Howells
2019-07-04 16:04       ` David Howells
2019-07-05  5:17       ` Greg Kroah-Hartman [this message]
2019-07-05  5:17         ` Greg Kroah-Hartman
2019-07-05  8:04         ` David Howells
2019-07-05  8:04           ` David Howells
2019-07-05  8:44           ` Greg Kroah-Hartman
2019-07-05  8:44             ` Greg Kroah-Hartman
2019-07-05 14:40             ` Alan Stern
2019-07-05 14:40               ` Alan Stern
2019-07-05 14:40               ` Alan Stern
2019-06-28 15:49 ` [PATCH 7/9] block: Add block layer notifications " David Howells
2019-06-28 15:49   ` David Howells
2019-06-28 15:49   ` David Howells
2019-06-28 15:49 ` [PATCH 8/9] usb: Add USB subsystem " David Howells
2019-06-28 15:49   ` David Howells
2019-06-28 15:49   ` David Howells
2019-07-03 17:07   ` Greg Kroah-Hartman
2019-07-03 17:07     ` Greg Kroah-Hartman
2019-06-28 15:49 ` [PATCH 9/9] Add sample notification program " David Howells
2019-06-28 15:49   ` David Howells
2019-06-28 15:49   ` 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=20190705051733.GA15821@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=casey@schaufler-ca.com \
    --cc=christian@brauner.io \
    --cc=dhowells@redhat.com \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=nicolas.dichtel@6wind.com \
    --cc=raven@themaw.net \
    --cc=sds@tycho.nsa.gov \
    --cc=viro@zeniv.linux.org.uk \
    /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.