All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Hutchings <ben.hutchings@codethink.co.uk>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Sasha Levin <Alexander.Levin@microsoft.com>,
	stable <stable@vger.kernel.org>
Subject: Re: [stable] i2c: dev: Fix the race between the release of i2c_dev and cdev
Date: Thu, 21 May 2020 21:58:57 +0100	[thread overview]
Message-ID: <1d4004d71924fa2e4c422ae086166c280e5b43be.camel@codethink.co.uk> (raw)
In-Reply-To: <20200521055011.GA2330588@kroah.com>

On Thu, 2020-05-21 at 07:50 +0200, Greg Kroah-Hartman wrote:
> On Wed, May 20, 2020 at 08:45:15PM +0100, Ben Hutchings wrote:
> > Please pick this fix for all stable branches:
> > 
> > commit 1413ef638abae4ab5621901cf4d8ef08a4a48ba6
> > Author: Kevin Hao <haokexin@gmail.com>
> > Date:   Fri Oct 11 23:00:14 2019 +0800
> > 
> >     i2c: dev: Fix the race between the release of i2c_dev and cdev
> > 
> > I don't know whether it will apply cleanly to all of them; I can deal
> > with those where it doesn't.
> 
> I applied it to 4.14, 4.19, 5.4, and 5.6.  It does apply to 4.9 but as
> the patch it depends on is not there, I don't think it will help.

It was included in 4.9.224, so both this and the similar watchdog fix
should be applicable for 4.9.

Ben.

-- 
Ben Hutchings, Software Developer                         Codethink Ltd
https://www.codethink.co.uk/                 Dale House, 35 Dale Street
                                     Manchester, M1 2HF, United Kingdom


  reply	other threads:[~2020-05-21 20:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-20 19:45 [stable] i2c: dev: Fix the race between the release of i2c_dev and cdev Ben Hutchings
2020-05-21  5:50 ` Greg Kroah-Hartman
2020-05-21 20:58   ` Ben Hutchings [this message]
2020-05-21 23:33     ` Sasha Levin
2020-05-22 11:34     ` Greg Kroah-Hartman

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=1d4004d71924fa2e4c422ae086166c280e5b43be.camel@codethink.co.uk \
    --to=ben.hutchings@codethink.co.uk \
    --cc=Alexander.Levin@microsoft.com \
    --cc=gregkh@linuxfoundation.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.