Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Luis Henriques <luis.henriques@canonical.com>
To: Jason Gerecke <killertofu@gmail.com>
Cc: "# v3.17+" <stable@vger.kernel.org>,
	Jiri Kosina <jikos@kernel.org>, Ping Cheng <pinglinux@gmail.com>,
	joshc@ni.com, Ioan-Adrian Ratiu <adi@adirat.com>
Subject: Re: Request "HID: usbhid: fix recursive deadlock" added to stable
Date: Wed, 3 Feb 2016 10:29:14 +0000	[thread overview]
Message-ID: <20160203102914.GA12337@charon.olymp> (raw)
In-Reply-To: <CANRwn3S6T1cG+8tYG-XZvWHHbP=DjXJB8E0sbPUOFz+yEi=L3g@mail.gmail.com>

On Wed, Jan 27, 2016 at 06:19:35PM -0800, Jason Gerecke wrote:
> This is to request that commit
> e470127e9606b1fa151c4184243e61296d1e0c0f be cherry-picked into the
> stable trees for Linux 3.17 and newer.
> 
> This commit fixes a deadlock which occurs when bringing a pen into
> proximity of the most recent generation of "Intuos" tablets
> (056a:033b, 056a:033c, 056a:033d, 056a:033d). The deadlock may be
> triggered on the stock 4.4 kernel, or any kernel dating back to 3.17
> if the backported "input-wacom" drivers are used. The cherry-picked
> commit has been tested successfully against what appear to be the
> currently-active trees: 3.18, 4.1, and 4.4.
>

Thanks, I'm queuing it for the 3.16 kernel as well.

Cheers,
--
Luís


> Jason
> ---
> Now instead of four in the eights place /
> you’ve got three, ‘Cause you added one  /
> (That is to say, eight) to the two,     /
> But you can’t take seven from three,    /
> So you look at the sixty-fours....
> --
> To unsubscribe from this list: send the line "unsubscribe stable" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2016-02-03 10:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-28  2:19 Request "HID: usbhid: fix recursive deadlock" added to stable Jason Gerecke
2016-01-28  9:48 ` Jiri Kosina
2016-02-03 10:29 ` Luis Henriques [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=20160203102914.GA12337@charon.olymp \
    --to=luis.henriques@canonical.com \
    --cc=adi@adirat.com \
    --cc=jikos@kernel.org \
    --cc=joshc@ni.com \
    --cc=killertofu@gmail.com \
    --cc=pinglinux@gmail.com \
    --cc=stable@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