mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Tejun Heo <tj@kernel.org>
Cc: linux-kernel@vger.kernel.org, rusty@rustcorp.com.au
Subject: Re: [PATCH] ida: make ida_simple_get/put() IRQ safe
Date: Fri, 28 Oct 2011 16:01:15 -0700	[thread overview]
Message-ID: <20111028160115.bba2b8cf.akpm@linux-foundation.org> (raw)
In-Reply-To: <20111026203311.GF24261@google.com>

On Wed, 26 Oct 2011 13:33:11 -0700
Tejun Heo <tj@kernel.org> wrote:

> It's often convenient to be able to release resource from IRQ context.
> Make ida_simple_*() use irqsave/restore spin ops so that they are IRQ
> safe.

The patch also accidentally makes ida_simple_get() callable from
interrupt context.  That's a somewhat unreliable operation due to
-ENOMEM possibilities even with GFP_ATOMIC.

> --- work.orig/lib/idr.c
> +++ work/lib/idr.c
> @@ -944,6 +944,7 @@ int ida_simple_get(struct ida *ida, unsi
>  {
>  	int ret, id;
>  	unsigned int max;
> +	unsigned long flags;
>  
>  	BUG_ON((int)start < 0);
>  	BUG_ON((int)end < 0);
> @@ -959,7 +960,7 @@ again:
>  	if (!ida_pre_get(ida, gfp_mask))
>  		return -ENOMEM;
>  
> -	spin_lock(&simple_ida_lock);
> +	spin_lock_irqsave(&simple_ida_lock, flags);
>  	ret = ida_get_new_above(ida, start, &id);
>  	if (!ret) {
>  		if (id > max) {
> @@ -969,7 +970,7 @@ again:
>  			ret = id;
>  		}
>  	}
> -	spin_unlock(&simple_ida_lock);
> +	spin_unlock_irqrestore(&simple_ida_lock, flags);
>  
>  	if (unlikely(ret == -EAGAIN))
>  		goto again;
> @@ -985,10 +986,12 @@ EXPORT_SYMBOL(ida_simple_get);
>   */
>  void ida_simple_remove(struct ida *ida, unsigned int id)
>  {
> +	unsigned long flags;
> +
>  	BUG_ON((int)id < 0);
> -	spin_lock(&simple_ida_lock);
> +	spin_lock_irqsave(&simple_ida_lock, flags);
>  	ida_remove(ida, id);
> -	spin_unlock(&simple_ida_lock);
> +	spin_unlock_irqrestore(&simple_ida_lock, flags);
>  }
>  EXPORT_SYMBOL(ida_simple_remove);

It didn't update the kerneldoc.  I wouldn't have bothered either ;)
We're generally bad about documenting permissible calling environments
and preconditions.


  reply	other threads:[~2011-10-28 23:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-26 20:33 Tejun Heo
2011-10-28 23:01 ` Andrew Morton [this message]
2011-10-28 23:11   ` Tejun Heo
2011-10-28 23:16     ` Andrew Morton

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=20111028160115.bba2b8cf.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=tj@kernel.org \
    /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

Powered by JetHome