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>,
intel-wired-lan@lists.osuosl.org, linux-gpio@vger.kernel.org,
netdev <netdev@vger.kernel.org>
Subject: [4.4] Security fixes (pinctrl, i40e, geneve)
Date: Wed, 11 Nov 2020 23:43:56 +0000 [thread overview]
Message-ID: <f5e2e87fb1a9613b161e63cf5504cc375e095dbc.camel@codethink.co.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 525 bytes --]
Here are backports of some fixes to the 4.4 stable branch.
I wasn't able to test the pinctrl fix (no idea how to reproduce it).
I wasn't able to test the i40e changes (no hardware and no reproducer
available).
I tested the geneve fix with libreswan as (roughly) described in the
commit message.
Ben.
--
Ben Hutchings, Software Developer Codethink Ltd
https://www.codethink.co.uk/ Dale House, 35 Dale Street
Manchester, M1 2HF, United Kingdom
[-- Attachment #2: security-4.4.mbox --]
[-- Type: application/mbox, Size: 12342 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Ben Hutchings <ben.hutchings@codethink.co.uk>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [4.4] Security fixes (pinctrl, i40e, geneve)
Date: Wed, 11 Nov 2020 23:43:56 +0000 [thread overview]
Message-ID: <f5e2e87fb1a9613b161e63cf5504cc375e095dbc.camel@codethink.co.uk> (raw)
Here are backports of some fixes to the 4.4 stable branch.
I wasn't able to test the pinctrl fix (no idea how to reproduce it).
I wasn't able to test the i40e changes (no hardware and no reproducer
available).
I tested the geneve fix with libreswan as (roughly) described in the
commit message.
Ben.
--
Ben Hutchings, Software Developer Codethink Ltd
https://www.codethink.co.uk/ Dale House, 35 Dale Street
Manchester, M1 2HF, United Kingdom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: security-4.4.mbox
Type: application/mbox
Size: 12342 bytes
Desc: not available
URL: <http://lists.osuosl.org/pipermail/intel-wired-lan/attachments/20201111/1d13b8f7/attachment.mbox>
next reply other threads:[~2020-11-12 1:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 23:43 Ben Hutchings [this message]
2020-11-11 23:43 ` [Intel-wired-lan] [4.4] Security fixes (pinctrl, i40e, geneve) Ben Hutchings
2020-11-12 16:13 ` Sasha Levin
2020-11-12 16:13 ` [Intel-wired-lan] " Sasha Levin
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=f5e2e87fb1a9613b161e63cf5504cc375e095dbc.camel@codethink.co.uk \
--to=ben.hutchings@codethink.co.uk \
--cc=Alexander.Levin@microsoft.com \
--cc=gregkh@linuxfoundation.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=linux-gpio@vger.kernel.org \
--cc=netdev@vger.kernel.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.