cip-dev.lists.cip-project.org archive mirror
 help / color / mirror / Atom feed
From: "Nobuhiro Iwamatsu" <nobuhiro1.iwamatsu@toshiba.co.jp>
To: <cip-dev@lists.cip-project.org>, <jan.kiszka@siemens.com>
Subject: Re: [cip-dev] Is CVE-2020-25284 backporting needed for 4.4-rt x86?
Date: Thu, 1 Oct 2020 09:39:26 +0000	[thread overview]
Message-ID: <OSBPR01MB29833C0DA59C4F77B159DE2492300@OSBPR01MB2983.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <TY2PR01MB4972E6442E2A10765AF7EBC4A03F0@TY2PR01MB4972.jpnprd01.prod.outlook.com>

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

Hi all,

> -----Original Message-----
> From: cip-dev@lists.cip-project.org [mailto:cip-dev@lists.cip-project.org] On Behalf Of
> masashi.kudo@cybertrust.co.jp
> Sent: Saturday, September 19, 2020 7:44 AM
> To: jan.kiszka@siemens.com; cip-dev@lists.cip-project.org
> Subject: Re: [cip-dev] Is CVE-2020-25284 backporting needed for 4.4-rt x86?
> 
> Hi, Jan-san,
> 
> Thanks for your quick response!
> 
> > Is that the only config in our repo carrying rbd/ceph? The we should likely drop
> > that, to be clear also in the future.
> 
> When we discussed at the IRC, the config carrying rbd/ceph is only 4.4-rt x86.
> 
> So, I understood that the backporting is not required.

I removed  CONFIG_BLK_DEV_RBD from 4.4.y-cip-rt/x86/siemens_i386-rt.config.

Best regards,
  Nobuhiro

[-- Attachment #2: Type: text/plain, Size: 420 bytes --]


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5490): https://lists.cip-project.org/g/cip-dev/message/5490
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]
-=-=-=-=-=-=-=-=-=-=-=-


      reply	other threads:[~2020-10-01  9:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-18 13:58 [cip-dev] Is CVE-2020-25284 backporting needed for 4.4-rt x86? masashi.kudo
2020-09-18 17:36 ` Jan Kiszka
2020-09-18 22:43   ` masashi.kudo
2020-10-01  9:39     ` Nobuhiro Iwamatsu [this message]

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=OSBPR01MB29833C0DA59C4F77B159DE2492300@OSBPR01MB2983.jpnprd01.prod.outlook.com \
    --to=nobuhiro1.iwamatsu@toshiba.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).