mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Artem Savkov <artem.savkov@gmail.com>
Cc: David Airlie <airlied@linux.ie>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] drm: missing idr_preload_end in drm_gem_flink_ioctl
Date: Tue, 12 Feb 2013 09:28:20 -0800	[thread overview]
Message-ID: <20130212172820.GC7348@htj.dyndns.org> (raw)
In-Reply-To: <1360496945-4694-1-git-send-email-artem.savkov@gmail.com>

(cc'ing Andrew)

Hello,

On Sun, Feb 10, 2013 at 03:49:05PM +0400, Artem Savkov wrote:
> Added missing idr_preload_end calls in drm_gem_flink_ioctl().
> Without those preemption stays disabled resulting in lots of "scheduling while
> atomic" BUGs.
> 
> Introduced in 4e486fae707d9a79c76f1be6dcacffc4a721cc1b (linux-next.git)
> 
> Signed-off-by: Artem Savkov <artem.savkov@gmail.com>
> ---
>  drivers/gpu/drm/drm_gem.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/drivers/gpu/drm/drm_gem.c b/drivers/gpu/drm/drm_gem.c
> index 6577514..f1700ef 100644
> --- a/drivers/gpu/drm/drm_gem.c
> +++ b/drivers/gpu/drm/drm_gem.c
> @@ -456,6 +456,7 @@ drm_gem_flink_ioctl(struct drm_device *dev, void *data,
>  		obj->name = ret;
>  		args->name = (uint64_t) obj->name;
>  		spin_unlock(&dev->object_name_lock);
> +		idr_preload_end();
>  
>  		if (ret < 0)
>  			goto err;
> @@ -465,6 +466,7 @@ drm_gem_flink_ioctl(struct drm_device *dev, void *data,
>  	} else {
>  		args->name = (uint64_t) obj->name;
>  		spin_unlock(&dev->object_name_lock);
> +		idr_preload_end();
>  		ret = 0;

Oops, sorry about that.

 Acked-by: Tejun Heo <tj@kernel.org>

Andrew, the original patch can be found at

 http://article.gmane.org/gmane.linux.kernel/1439101/raw

Thanks.

-- 
tejun

      reply	other threads:[~2013-02-12 17:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-10 11:49 Artem Savkov
2013-02-12 17:28 ` Tejun Heo [this message]

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=20130212172820.GC7348@htj.dyndns.org \
    --to=tj@kernel.org \
    --cc=airlied@linux.ie \
    --cc=akpm@linux-foundation.org \
    --cc=artem.savkov@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.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

all inboxes | Powered by JetHome®