mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Vasiliy Kulikov <segoon@openwall.com>
Cc: linux-kernel@vger.kernel.org, Vasiliy Kulikov <segooon@gmail.com>,
	Balbir Singh <balbir@linux.vnet.ibm.com>,
	Balbir Singh <bsingharora@gmail.com>
Subject: Re: [PATCH v2] taskstats: don't allow duplicate entries in listener mode
Date: Tue, 21 Jun 2011 15:49:00 -0700	[thread overview]
Message-ID: <20110621154900.ea6b8839.akpm@linux-foundation.org> (raw)
In-Reply-To: <1308239759-4797-1-git-send-email-segoon@openwall.com>

On Thu, 16 Jun 2011 19:55:59 +0400
Vasiliy Kulikov <segoon@openwall.com> wrote:

> Currently a single process may register exit handlers unlimited times.
> It may lead to a bloated listeners chain and very slow process terminations.
> E.g. after 10KK sent TASKSTATS_CMD_ATTR_REGISTER_CPUMASKs ~300 Mb of
> kernel memory is stolen for the handlers chain and "time id" shows 2-7
> seconds instead of normal 0.003.  It makes it possible to exhaust all
> kernel memory and to eat much of CPU time by triggerring numerous exits
> on a single CPU.
> 
> The patch limits the number of times a single process may register
> itself on a single CPU to one.
> 
> One little issue is kept unfixed - as taskstats_exit() is called before
> exit_files() in do_exit(), the orphaned listener entry (if it was not
> explicitly deregistered) is kept until the next someone's exit() and
> implicit deregistration in send_cpu_listeners().  So, if a process
> registered itself as a listener exits and the next spawned process gets
> the same pid, it would inherit taskstats attributes.

ow. That's an unprivileged operation, isn't it?

> 
> diff --git a/kernel/taskstats.c b/kernel/taskstats.c
> index 9ffea36..fc0f220 100644
> --- a/kernel/taskstats.c
> +++ b/kernel/taskstats.c
> @@ -285,16 +285,18 @@ ret:
>  static int add_del_listener(pid_t pid, const struct cpumask *mask, int isadd)
>  {
>  	struct listener_list *listeners;
> -	struct listener *s, *tmp;
> +	struct listener *s, *tmp, *s2;
>  	unsigned int cpu;
>  
>  	if (!cpumask_subset(mask, cpu_possible_mask))
>  		return -EINVAL;
>  
> +	s = NULL;
>  	if (isadd == REGISTER) {
>  		for_each_cpu(cpu, mask) {
> -			s = kmalloc_node(sizeof(struct listener), GFP_KERNEL,
> -					 cpu_to_node(cpu));
> +			if (!s)
> +				s = kmalloc_node(sizeof(struct listener),
> +						 GFP_KERNEL, cpu_to_node(cpu));
>  			if (!s)
>  				goto cleanup;
>  			s->pid = pid;
> @@ -303,9 +305,16 @@ static int add_del_listener(pid_t pid, const struct cpumask *mask, int isadd)
>  
>  			listeners = &per_cpu(listener_array, cpu);
>  			down_write(&listeners->sem);
> +			list_for_each_entry_safe(s2, tmp, &listeners->list, list) {
> +				if (s2->pid == pid)
> +					goto next_cpu;
> +			}
>  			list_add(&s->list, &listeners->list);
> +			s = NULL;
> +next_cpu:
>  			up_write(&listeners->sem);
>  		}
> +		kfree(s);
>  		return 0;
>  	}
>  


  reply	other threads:[~2011-06-21 22:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-16 15:55 Vasiliy Kulikov
2011-06-21 22:49 ` Andrew Morton [this message]
2011-06-22  6:54   ` Vasiliy Kulikov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110621154900.ea6b8839.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=bsingharora@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=segoon@openwall.com \
    --cc=segooon@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®