[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1782773.1596460942@warthog.procyon.org.uk>
Date: Mon, 03 Aug 2020 14:22:22 +0100
From: David Howells <dhowells@...hat.com>
To: viro@...iv.linux.org.uk
Cc: dhowells@...hat.com, linux-security-module@...r.kernel.org,
Stephen Smalley <sds@...ho.nsa.gov>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Casey Schaufler <casey@...aufler-ca.com>,
Miklos Szeredi <mszeredi@...hat.com>,
Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>,
James Morris <jamorris@...ux.microsoft.com>,
nicolas.dichtel@...nd.com, raven@...maw.net, christian@...uner.io,
jlayton@...hat.com, kzak@...hat.com, linux-api@...r.kernel.org,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/5] Mount notifications [ver #2]
David Howells <dhowells@...hat.com> wrote:
>
> ===================
> SIGNIFICANT CHANGES
> ===================
>
> ver #2:
>
> (*) Make the ID fields in the mount notification 64-bits. They're left
> referring to the mount ID here, but switched to the mount unique ID in
> the patch in fsinfo that adds that. [Requested by Miklós Szeredi]
>
> (*) Dropped the event counters from the mount notification message.
> [Requested by Miklós].
>
> This can easily be added back later as the message length can be
> increased to show it.
>
> (*) Moved the mount event counters over to the fsinfo patchset.
Also:
(*) Added limitations on the number of concurrent watches that can be held
by a user. [Requested by Linus]
(*) Removed the unused NOTIFY_MOUNT_IS_RECURSIVE flag. [Requested by
Miklós]
David
Powered by blists - more mailing lists