Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Ben Hutchings <ben.hutchings@codethink.co.uk>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Sasha Levin <Alexander.Levin@microsoft.com>
Cc: stable <stable@vger.kernel.org>
Subject: [4.4] Security fixes
Date: Thu, 21 May 2020 23:20:01 +0100	[thread overview]
Message-ID: <cd7a780e9fad63868960562ca2e59383d03081c3.camel@codethink.co.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 705 bytes --]

I've backported fixes for I²C and media controller devices, dealing
with the lifetime of related cdev and struct device instances and some
similar race conditions.  Fixing the lifetime issue for watchdog
devices looks impractical for 4.4, as it depends on a big refactoring
in 4.5.

All but one of these are already included in or queued for the later
stable branches.  You dropped the I²C lifetime fix for 4.9, but I hope 
my previous replies persuaded you that it is valid.

Ben.

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

[-- Attachment #2: 4.4-security.mboxz --]
[-- Type: application/mbox, Size: 54022 bytes --]

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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-21 22:20 Ben Hutchings [this message]
2020-05-21 23:36 ` [4.4] Security fixes Sasha Levin
  -- strict thread matches above, loose matches on Subject: below --
2019-05-30 14:22 Ben Hutchings
2019-06-04 14:50 ` 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=cd7a780e9fad63868960562ca2e59383d03081c3.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox