cip-dev.lists.cip-project.org archive mirror
 help / color / mirror / Atom feed
From: "florian.bezdeka@siemens.com" <florian.bezdeka@siemens.com>
To: "cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
	"pavel@denx.de" <pavel@denx.de>
Cc: "jan.kiszka@siemens.com" <jan.kiszka@siemens.com>,
	"nobuhiro1.iwamatsu@toshiba.co.jp"
	<nobuhiro1.iwamatsu@toshiba.co.jp>,
	"masashi.kudo@cybertrust.co.jp" <masashi.kudo@cybertrust.co.jp>
Subject: Re: [cip-dev] Cip-kernel-sec Updates for Week of 2021-02-18
Date: Thu, 18 Feb 2021 16:28:55 +0000	[thread overview]
Message-ID: <d5665f714ddfbe257446b9bc3d6dcda18e86f67d.camel@siemens.com> (raw)
In-Reply-To: <CAGb2v66RODCVTdiway7SiNVQHDcgFiVHH0XYJmktQSa+_hdFnQ@mail.gmail.com>

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

On Thu, 2021-02-18 at 17:52 +0800, Chen-Yu Tsai (Moxa) wrote:
> On Thu, Feb 18, 2021 at 5:49 PM Pavel Machek <pavel@denx.de> wrote:
> > 
> > On Thu 2021-02-18 17:21:57, Chen-Yu Tsai wrote:
> > > Hi everyone,
> > > 
> > > Five new issues this week:
> > > 
> > > CVE-2021-20239 [setsockopt copy_from_user error] - fixed in 5.4 and
> > > removed from 5.10
> > > CVE-2021-26930 [xen-blkback error handling] - PR sent
> > > CVE-2021-26931 [xen backends: BUG_ON in error handling] - PR sent
> > > CVE-2021-26932 [xen grant mapping error handling] - PR sent
> > > CVE-2021-26934 [xen unsupported driver] - Xen documentation change
> > > stating be-alloc display driver is unsupported
> > > 
> > > Linus doesn't seem to be processing PRs for the new merge window yet,
> > > so we might have to wait a while before the Xen ones are fixed and
> > > backported.
> > 
> > Well, Xen is not a typical thing to run on embbeded hardware, but I
> > did not check the configs.
> 
> I see Renesas and Siemens have it enabled. Is Xen still relevant?
> Or has everyone switched over to KVM + QEMU?

Where is the mentioned kernel config located? I wasn't able to find the
correct git tree. 

We already had a short internal discussion and are quite sure that we
don't need it. Just point me to the configuration. We will review again
and come up with the necessary patch to disable it.

> 
> > It seems Linus is having power problems:
> 
> I read the headline on Phoronix, but didn't know it was this bad.
> That also explains why lkml.org was completely empty yesterday.
> 
> 
> ChenYu
> 
> > Best regards,
> >                                                                 Pavel
> > 
> > Date: Tue, 16 Feb 2021 12:25:06 -0800
> > From: Linus Torvalds <torvalds@linuxfoundation.org>
> > To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
> > Cc: users@linux.kernel.org
> > Subject: Re: [kernel.org users] Partial power outage in the PDX
> > datacentre
> > 
> > [-- Attachment #1 --]
> > [-- Type: multipart/alternative, Encoding: 7bit, Size: 2.2K --]
> > 
> > Sadly, the power at my house is still entirely out, although cell
> > service
> > has now been fixed so at least I can read some email without walking
> > outside.
> > 
> > But with no power for my laptop or workstation, I won't be starting
> > the
> > merge window until power is back more widely in they Portland area.
> > 
> > My neighborhood is likely not a priority, so it very possibly will be
> > a few
> > more days (so far without power since Sunday evening).
> > 
> > Even the local highway 43 (ok, not a big highway, but still) is still
> > closed down two days later due to downed trees.
> > 
> >         Linus
> > 
> > 
> > --
> > DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
> > HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> 
> 


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


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#6185): https://lists.cip-project.org/g/cip-dev/message/6185
Mute This Topic: https://lists.cip-project.org/mt/80725760/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:[~2021-02-18 16:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-18  9:21 [cip-dev] Cip-kernel-sec Updates for Week of 2021-02-18 Chen-Yu Tsai (Moxa)
2021-02-18  9:49 ` Pavel Machek
2021-02-18  9:52   ` Chen-Yu Tsai (Moxa)
2021-02-18 16:28     ` florian.bezdeka [this message]
2021-02-18 18:34       ` Pavel Machek
2021-02-24 12:42         ` [cip-dev][cip-kernel-config] 1/2] 4.19.y-cip: Remove XEN guest support for siemens_ipc227e florian.bezdeka
2021-02-24 12:43         ` [cip-dev][cip-kernel-config] 2/2] 5.10.y-cip: Removing " florian.bezdeka
2021-02-24 12:50         ` [cip-dev][cip-kernel-config][PATCH v2 1/2] 4.19.y-cip: Remove " florian.bezdeka
2021-02-25  8:58           ` Nobuhiro Iwamatsu
2021-02-24 12:50         ` [cip-dev][cip-kernel-config][PATCH v2 2/2] 5.10.y-cip: Removing " florian.bezdeka

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=d5665f714ddfbe257446b9bc3d6dcda18e86f67d.camel@siemens.com \
    --to=florian.bezdeka@siemens.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=jan.kiszka@siemens.com \
    --cc=masashi.kudo@cybertrust.co.jp \
    --cc=nobuhiro1.iwamatsu@toshiba.co.jp \
    --cc=pavel@denx.de \
    /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).