All of lore.kernel.org
 help / color / mirror / Atom feed
From: jan.kiszka@siemens.com (Jan Kiszka)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Meltdown and Spectre in CIP
Date: Fri, 2 Mar 2018 18:52:19 +0100	[thread overview]
Message-ID: <32855182-84ed-f190-d5b8-b5c166a4749c@siemens.com> (raw)
In-Reply-To: <1518695091.3422.24.camel@codethink.co.uk>

On 2018-02-15 12:44, Ben Hutchings wrote:
> [...]
>> Will you be keeping an eye on Spectre patches on behalf of CIP as
>> part of your maintainer role? I guess you may be in the loop a bit
>> more than the rest of us?
> 
> I will look at the mitigations as they land upstream, but I still think
> these are low priority security issues for CIP.

The priority starts to rise here because new system are coming out that
need to start system testing and other processes on a CIP kernel with
Spectre mitigations (x86 so far). Can you estimate the time needed for a
cip19 release?

Thanks,
Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

  reply	other threads:[~2018-03-02 17:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-10 14:16 [cip-dev] Meltdown and Spectre in CIP Ben Hutchings
2018-01-16  8:01 ` Chris Paterson
2018-02-15 11:44   ` Ben Hutchings
2018-03-02 17:52     ` Jan Kiszka [this message]
2018-03-08 22:45 ` 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=32855182-84ed-f190-d5b8-b5c166a4749c@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=cip-dev@lists.cip-project.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.