Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1454681
| From | "J. Bruce Fields" <bfields@fieldses.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [RFC PATCH] locks: Show only file_locks created in the same pidns as current process |
| Date | 2016-08-02 17:10 +0200 |
| Message-ID | <s1Jup-68b-7@gated-at.bofh.it> (permalink) |
| References | <s1JkK-5Nl-35@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Tue, Aug 02, 2016 at 05:42:23PM +0300, Nikolay Borisov wrote:
> Currently when /proc/locks is read it will show all the file locks
> which are currently created on the machine. On containers, hosted
> on busy servers this means that doing lsof can be very slow. I
> observed up to 5 seconds stalls reading 50k locks,
Do you mean just that the reading process itself was blocked, or that
others were getting stuck on blocked_lock_lock?
(And what process was actually reading /proc/locks, out of curiosity?)
> while the container
> itself had only a small number of relevant entries. Fix it by
> filtering the locks listed by the pidns of the current process
> and the process which created the lock.
Thanks, that's interesting. So you show a lock if it was created by
someone in the current pid namespace. With a special exception for the
init namespace so that
If a filesystem is shared between containers that means you won't
necessarily be able to figure out from within a container which lock is
conflicting with your lock. (I don't know if that's really a problem.
I'm unfortunately short on evidence aobut what people actually use
/proc/locks for....)
--b.
>
> Signed-off-by: Nikolay Borisov <kernel@kyup.com>
> ---
> fs/locks.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/fs/locks.c b/fs/locks.c
> index 6333263b7bc8..53e96df4c583 100644
> --- a/fs/locks.c
> +++ b/fs/locks.c
> @@ -2615,9 +2615,17 @@ static int locks_show(struct seq_file *f, void *v)
> {
> struct locks_iterator *iter = f->private;
> struct file_lock *fl, *bfl;
> + struct pid_namespace *pid_ns = task_active_pid_ns(current);
> +
>
> fl = hlist_entry(v, struct file_lock, fl_link);
>
> + pr_info ("Current pid_ns: %p init_pid_ns: %p, fl->fl_nspid: %p nspidof:%p\n", pid_ns, &init_pid_ns,
> + fl->fl_nspid, ns_of_pid(fl->fl_nspid));
> + if ((pid_ns != &init_pid_ns) && fl->fl_nspid &&
> + (pid_ns != ns_of_pid(fl->fl_nspid)))
> + return 0;
> +
> lock_get_status(f, fl, iter->li_pos, "");
>
> list_for_each_entry(bfl, &fl->fl_block, fl_block)
> --
> 2.5.0
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[RFC PATCH] locks: Show only file_locks created in the same pidns as current process Nikolay Borisov <kernel@kyup.com> - 2016-08-02 17:00 +0200
Re: [RFC PATCH] locks: Show only file_locks created in the same pidns as current process "J. Bruce Fields" <bfields@fieldses.org> - 2016-08-02 17:10 +0200
Re: [RFC PATCH] locks: Show only file_locks created in the same pidns as current process Nikolay Borisov <kernel@kyup.com> - 2016-08-02 17:50 +0200
Re: [RFC PATCH] locks: Show only file_locks created in the same pidns as current process "J. Bruce Fields" <bfields@fieldses.org> - 2016-08-02 18:40 +0200
Re: [RFC PATCH] locks: Show only file_locks created in the same pidns as current process ebiederm@xmission.com (Eric W. Biederman) - 2016-08-02 18:20 +0200
Re: [RFC PATCH] locks: Show only file_locks created in the same pidns as current process "J. Bruce Fields" <bfields@fieldses.org> - 2016-08-02 19:50 +0200
Re: [RFC PATCH] locks: Show only file_locks created in the same pidns as current process ebiederm@xmission.com (Eric W. Biederman) - 2016-08-02 21:30 +0200
Re: [RFC PATCH] locks: Show only file_locks created in the same pidns as current process "J. Bruce Fields" <bfields@fieldses.org> - 2016-08-02 22:00 +0200
Re: [RFC PATCH] locks: Show only file_locks created in the same pidns as current process Jeff Layton <jlayton@poochiereds.net> - 2016-08-02 22:10 +0200
Re: [RFC PATCH] locks: Show only file_locks created in the same pidns as current process Nikolay Borisov <kernel@kyup.com> - 2016-08-02 22:20 +0200
Re: [RFC PATCH] locks: Show only file_locks created in the same pidns as current process "J. Bruce Fields" <bfields@fieldses.org> - 2016-08-02 22:50 +0200
[PATCH v2] locks: Filter /proc/locks output on proc pid ns Nikolay Borisov <kernel@kyup.com> - 2016-08-03 10:00 +0200
Re: [PATCH v2] locks: Filter /proc/locks output on proc pid ns Jeff Layton <jlayton@poochiereds.net> - 2016-08-03 15:50 +0200
Re: [PATCH v2] locks: Filter /proc/locks output on proc pid ns "J. Bruce Fields" <bfields@fieldses.org> - 2016-08-03 16:30 +0200
Re: [PATCH v2] locks: Filter /proc/locks output on proc pid ns Nikolay Borisov <kernel@kyup.com> - 2016-08-03 16:40 +0200
Re: [PATCH v2] locks: Filter /proc/locks output on proc pid ns Nikolay Borisov <kernel@kyup.com> - 2016-08-03 16:30 +0200
Re: [PATCH v2] locks: Filter /proc/locks output on proc pid ns Nikolay Borisov <kernel@kyup.com> - 2016-08-03 17:10 +0200
Re: [PATCH v2] locks: Filter /proc/locks output on proc pid ns "J. Bruce Fields" <bfields@fieldses.org> - 2016-08-03 17:20 +0200
Re: [PATCH v2] locks: Filter /proc/locks output on proc pid ns Nikolay Borisov <kernel@kyup.com> - 2016-08-03 17:20 +0200
Re: [PATCH v2] locks: Filter /proc/locks output on proc pid ns ebiederm@xmission.com (Eric W. Biederman) - 2016-08-03 19:50 +0200
csiph-web