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>,
	Sasha Levin <Alexander.Levin@microsoft.com>
Cc: stable <stable@vger.kernel.org>
Subject: Security fixes for 4.4
Date: Thu, 13 Dec 2018 18:51:19 +0000	[thread overview]
Message-ID: <1544727079.19315.55.camel@codethink.co.uk> (raw)

I've backported a number of fixes for security issues affecting 4.4-
stable.  All of these are already fixed in the newer stable branches.

For the BPF fix, I verified that the self-tests (taken from 4.14)
didn't regress and temporarily added logging to check that the
mitigation is applied when needed.

For the KVM changes, I verified that IBPB/IBRS are now exposed to and
used by a guest on Intel hardware.

I also verified that the current self-tests for timers, usercopy and vm
didn't regress.

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:[~2018-12-13 18:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-13 18:51 Ben Hutchings [this message]
2018-12-13 18:52 ` Security fixes for 4.4 Ben Hutchings
2018-12-13 19:13 ` Greg Kroah-Hartman
  -- strict thread matches above, loose matches on Subject: below --
2017-11-15 21:10 Ben Hutchings
2017-11-16 11:29 ` Greg Kroah-Hartman
2017-11-16 22:07   ` Theodore Ts'o
2017-11-17  8:10     ` Greg Kroah-Hartman
2017-11-17 13:30     ` Ben Hutchings
2017-11-20 14:02       ` Jan Kara
2017-11-17 12:06   ` Ben Hutchings
2017-11-17 12:25     ` Greg Kroah-Hartman
2017-11-16 11:31 ` Greg Kroah-Hartman
2017-11-16 11:32   ` Paolo Bonzini
2017-11-16 13:28     ` Greg Kroah-Hartman
2017-11-16 11:33 ` Greg Kroah-Hartman
2017-11-16 11:33 ` Greg Kroah-Hartman
2017-11-16 11:34 ` Greg Kroah-Hartman
2017-11-19 10:18 ` 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=1544727079.19315.55.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.