linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Oliver Neukum <oliver@neukum.org>
Cc: Daniel Ritz <daniel.ritz@gmx.ch>,
	linux-input@vger.kernel.org, USB list <linux-usb@vger.kernel.org>
Subject: Re: [RFC/RFT 3/5] USB: usbtouch: Prevent possible deadlock
Date: Sun, 14 Mar 2010 00:59:49 -0800	[thread overview]
Message-ID: <20100314085949.GC8226@core.coreip.homeip.net> (raw)
In-Reply-To: <201003121542.53537.oliver@neukum.org>

Hi Oliver,

On Fri, Mar 12, 2010 at 03:42:53PM +0100, Oliver Neukum wrote:
> From 5e4fc75d1031ca1c621c0f85cf1e903ffd8fb758 Mon Sep 17 00:00:00 2001
> From: Oliver Neukum <oliver@neukum.org>
> Date: Thu, 11 Mar 2010 15:06:51 +0100
> Subject: [PATCH 3/5] USB: usbtouch: Prevent possible deadlock
> 
> For autosuspend memory in suspend/resume must be allocated with
> GFP_NOIO.

I'd prefer if this change was folded into previous patch - there was no
deadlock condition before you added reset_resume.

> @@ -806,19 +806,19 @@ static int nexio_init(struct usbtouch_usb *usbtouch)
>  	/* prepare ACK URB */
>  	ret = -ENOMEM;
>  
> -	usbtouch->priv = kmalloc(sizeof(struct nexio_priv), GFP_KERNEL);
> +	usbtouch->priv = kmalloc(sizeof(struct nexio_priv), GFP_NOIO);
>  	if (!usbtouch->priv)
>  		goto out_buf;
>  

Remind me, how does ->exit() gets called in case of reset_resume?
Otherwise it looks like ne are leaking memory...

-- 
Dmitry

  reply	other threads:[~2010-03-14  8:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-12 14:42 [RFC/RFT 3/5] USB: usbtouch: Prevent possible deadlock Oliver Neukum
2010-03-14  8:59 ` Dmitry Torokhov [this message]
     [not found]   ` <20100314085949.GC8226-WlK9ik9hQGAhIp7JRqBPierSzoNAToWh@public.gmane.org>
2010-03-14  9:12     ` Oliver Neukum

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=20100314085949.GC8226@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=daniel.ritz@gmx.ch \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=oliver@neukum.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;
as well as URLs for NNTP newsgroup(s).