From: Ben Hutchings <ben.hutchings@codethink.co.uk>
To: nobuhiro1.iwamatsu@toshiba.co.jp, pavel@ucw.cz,
cip-dev@lists.cip-project.org, Chris.Paterson2@renesas.com
Subject: Re: [cip-dev] [backport 4.4] mac80211: Fix TKIP replay protection immediately after key setup
Date: Fri, 20 Mar 2020 21:42:24 +0000 [thread overview]
Message-ID: <429a5416450240c08907d5e7bfc772f326b0c4e4.camel@codethink.co.uk> (raw)
In-Reply-To: <OSAPR01MB366764C9C68FDC11C0D5EFAC92160@OSAPR01MB3667.jpnprd01.prod.outlook.com>
On Mon, 2020-02-17 at 23:14 +0000, nobuhiro1.iwamatsu@toshiba.co.jp wrote:
> Hi Pavel,
>
> > -----Original Message-----
> > From: cip-dev [mailto:cip-dev-bounces@lists.cip-project.org] On Behalf
> > Of Pavel Machek
> > Sent: Sunday, February 16, 2020 4:54 AM
> > To: cip-dev@lists.cip-project.org; Chris.Paterson2@renesas.com
> > Subject: [cip-dev] [backport 4.4] mac80211: Fix TKIP replay protection
> > immediately after key setup
> >
> > Hi!
> >
> > So... this is first backport patch. I'll need to reformat a changelog.
> >
> > The patch should pass our tests on gitlab, but I somehow don't think those
> > tests involved wifi at all... At least it compiles.
> >
> > Can someone test it easily? Should I just submit it to stable explaining
> > I did not test it?
>
> If testing is difficult, how about sending a patch to stable ML as RFC?
> We may get reviews from the patch authors.
>
> > Do you have other patches that should go to 4.4/4.19?
> >
>
> I don't think there are other patches.
The security tracker shows a lot of fixes missing from 4.4.
Ben.
--
Ben Hutchings, Software Developer Codethink Ltd
https://www.codethink.co.uk/ Dale House, 35 Dale Street
Manchester, M1 2HF, United Kingdom
_______________________________________________
cip-dev mailing list
cip-dev@lists.cip-project.org
https://lists.cip-project.org/mailman/listinfo/cip-dev
next prev parent reply other threads:[~2020-03-20 21:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-15 19:54 [cip-dev] [backport 4.4] mac80211: Fix TKIP replay protection immediately after key setup Pavel Machek
2020-02-17 23:14 ` nobuhiro1.iwamatsu at toshiba.co.jp
2020-03-20 21:42 ` Ben Hutchings [this message]
2020-03-20 21:41 ` Ben Hutchings
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=429a5416450240c08907d5e7bfc772f326b0c4e4.camel@codethink.co.uk \
--to=ben.hutchings@codethink.co.uk \
--cc=Chris.Paterson2@renesas.com \
--cc=cip-dev@lists.cip-project.org \
--cc=nobuhiro1.iwamatsu@toshiba.co.jp \
--cc=pavel@ucw.cz \
/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.