[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2189056.1595620785@warthog.procyon.org.uk>
Date: Fri, 24 Jul 2020 20:59:45 +0100
From: David Howells <dhowells@...hat.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: dhowells@...hat.com, Al Viro <viro@...iv.linux.org.uk>,
Casey Schaufler <casey@...aufler-ca.com>,
Stephen Smalley <sds@...ho.nsa.gov>,
Nicolas Dichtel <nicolas.dichtel@...nd.com>,
Ian Kent <raven@...maw.net>,
Christian Brauner <christian@...uner.io>,
Jeff Layton <jlayton@...hat.com>, Karel Zak <kzak@...hat.com>,
Miklos Szeredi <mszeredi@...hat.com>,
Linux API <linux-api@...r.kernel.org>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
LSM List <linux-security-module@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 3/4] watch_queue: Implement mount topology and attribute change notifications
Linus Torvalds <torvalds@...ux-foundation.org> wrote:
> So now you can basically allocate as much kernel memory as you want as
> a regular user, as long as you have a mounted directory you can walk
> (ie everybody).
>
> Is there any limiting of watches anywhere? I don't see it.
That's a good point. Any suggestions on how to do it? An additional RLIMIT?
Or should I do it like I did with keyrings and separately manage a quota for
each user?
David
Powered by blists - more mailing lists