From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Ben Hutchings <ben.hutchings@codethink.co.uk>
Cc: stable <stable@vger.kernel.org>,
David Eccher <d.eccher@gmail.com>, Felipe Balbi <balbi@ti.com>
Subject: Re: [3.18-stable] Revert "usb: gadget: inode.c: fix unbalanced spin_lock in ep0_write"
Date: Tue, 17 Oct 2017 16:15:30 +0200 [thread overview]
Message-ID: <20171017141530.GA4025@kroah.com> (raw)
In-Reply-To: <1508244958.22379.63.camel@codethink.co.uk>
On Tue, Oct 17, 2017 at 01:55:58PM +0100, Ben Hutchings wrote:
> Please revert commit abb540b53976 ("usb: gadget: inode.c: fix
> unbalanced spin_lock in ep0_write") on the 3.18 stable branch. The
> upstream commit (b7bd98b7db9f) fixed a bug introduced in 4.0 by commit
> 96b62a571934 ("gadgetfs: really get rid of switching ->f_op").
> Backporting it to older versions introduces a lock unbalance.
Ugh, you are right, this was my fault, and kbuild also complained about
this.
now reverted.
greg k-h
prev parent reply other threads:[~2017-10-17 14:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 12:55 [3.18-stable] Revert "usb: gadget: inode.c: fix unbalanced spin_lock in ep0_write" Ben Hutchings
2017-10-17 14:15 ` Greg Kroah-Hartman [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=20171017141530.GA4025@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=balbi@ti.com \
--cc=ben.hutchings@codethink.co.uk \
--cc=d.eccher@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;
as well as URLs for NNTP newsgroup(s).