[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wgWNpzCuHyyFwhR2fq49yxB9tKiH2t2y-O-8V6Gh0TFdw@mail.gmail.com>
Date: Fri, 24 Jul 2020 13:25:50 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: David Howells <dhowells@...hat.com>
Cc: 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
On Fri, Jul 24, 2020 at 12:59 PM David Howells <dhowells@...hat.com> wrote:
>
> 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?
I'd count them per user, and maybe start out saying "you can have as
many watches as you can have files" and just re-use RLIMIT_NOFILE as
the limit for them.
And if that causes problems, let's re-visit. How does that sound?
Linus
Powered by blists - more mailing lists