[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.44L0.1907051038550.1606-100000@iolanthe.rowland.org>
Date: Fri, 5 Jul 2019 10:40:36 -0400 (EDT)
From: Alan Stern <stern@...land.harvard.edu>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
cc: David Howells <dhowells@...hat.com>, <viro@...iv.linux.org.uk>,
Casey Schaufler <casey@...aufler-ca.com>,
Stephen Smalley <sds@...ho.nsa.gov>,
<nicolas.dichtel@...nd.com>, <raven@...maw.net>,
Christian Brauner <christian@...uner.io>,
<keyrings@...r.kernel.org>, <linux-usb@...r.kernel.org>,
<linux-security-module@...r.kernel.org>,
<linux-fsdevel@...r.kernel.org>, <linux-api@...r.kernel.org>,
<linux-block@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 6/9] Add a general, global device notification watch list
[ver #5]
On Fri, 5 Jul 2019, Greg Kroah-Hartman wrote:
> On Fri, Jul 05, 2019 at 09:04:17AM +0100, David Howells wrote:
> > Greg Kroah-Hartman <gregkh@...uxfoundation.org> wrote:
> >
> > > Hm, good point, but there should be some way to test this to verify it
> > > works. Maybe for the other types of events?
> >
> > Keyrings is the simplest. keyutils's testsuite will handle that. I'm trying
> > to work out if I can simply make every macro in there that does a modification
> > perform a watch automatically to make sure the appropriate events happen.
>
> That should be good enough to test the basic functionality. After this
> gets merged I'll see if I can come up with a way to test the USB
> stuff...
You can create USB connect and disconnect events programmatically by
using dummy-hcd with gadget-zero. Turning off the port's POWER feature
will cause a disconnect, and turning it back on will cause a connect.
Alan Stern
Powered by blists - more mailing lists