From: "masashi.kudo@cybertrust.co.jp" <masashi.kudo@cybertrust.co.jp>
To: <jan.kiszka@siemens.com>, <cip-dev@lists.cip-project.org>
Subject: [cip-dev] Is CVE-2020-25284 backporting needed for 4.4-rt x86?
Date: Fri, 18 Sep 2020 13:58:00 +0000 [thread overview]
Message-ID: <TY2PR01MB49720A7CA0EC8E349A473CFFA03F0@TY2PR01MB4972.jpnprd01.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 592 bytes --]
Hi, Jan-san, Siemens team,
There was some query to Siemens about the need of CVE-2020-25284 backporting.
- CVE-2020-25284 is in rbd ( Ceph block device ).
- it is only fixed for v4.19 and later stable kernels
- Siemens has this built as a module in their 4.4-rt x86 config, but not their 4.19 one
So the question from the Kernel Team is whether Siemens needs its backporting to 4.4-rt or not.
Please take a look about the discussion at the IRC meeting yesterday.
https://irclogs.baserock.org/meetings/cip/2020/09/cip.2020-09-17-09.00.log.html
Best regards,
--
M. Kudo
[-- Attachment #2: Type: text/plain, Size: 420 bytes --]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5464): https://lists.cip-project.org/g/cip-dev/message/5464
Mute This Topic: https://lists.cip-project.org/mt/76930681/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-
next reply other threads:[~2020-09-18 13:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 13:58 masashi.kudo [this message]
2020-09-18 17:36 ` [cip-dev] Is CVE-2020-25284 backporting needed for 4.4-rt x86? Jan Kiszka
2020-09-18 22:43 ` masashi.kudo
2020-10-01 9:39 ` Nobuhiro Iwamatsu
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=TY2PR01MB49720A7CA0EC8E349A473CFFA03F0@TY2PR01MB4972.jpnprd01.prod.outlook.com \
--to=masashi.kudo@cybertrust.co.jp \
--cc=cip-dev@lists.cip-project.org \
--cc=jan.kiszka@siemens.com \
/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;
as well as URLs for NNTP newsgroup(s).