[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <12946.1562313857@warthog.procyon.org.uk>
Date: Fri, 05 Jul 2019 09:04:17 +0100
From: David Howells <dhowells@...hat.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: 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]
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.
David
Powered by blists - more mailing lists