public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: "Pavel Machek" <pavel@denx.de>
To: Pavel Machek <pavel@denx.de>
Cc: Chen-Yu Tsai <wens@csie.org>,
	cip-dev@lists.cip-project.org,
	Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>
Subject: Re: [cip-dev] cip-kernel-sec Updates for Last Week of October
Date: Mon, 2 Nov 2020 22:12:25 +0100	[thread overview]
Message-ID: <20201102211225.GA2874@duo.ucw.cz> (raw)
In-Reply-To: <20201102113906.GC9840@duo.ucw.cz>


[-- Attachment #1.1: Type: text/plain, Size: 1676 bytes --]

Hi!

> > - Fix for CVE-2020-27673 has not been backported yet.
> 
> Some kind of Xen issue, not really relevant to us, and fix is not
> easy.
> 
> I'd say we can ignore this one.

This is queued for 4.19.155:

 | a9d6e970261d 0891fb39ba67 o: | xen/events: don't use chip_data for legacy IRQs
 | d103e667bb8c 073d0552ead5 o: | xen/events: avoid removing an event channel while handling it
 | ed86a5182306 4d3fe31bd993 o: | xen/events: add a proper barrier to 2-level uevent unmasking
 | 6e894d279f4e f01337197419 o: | xen/events: fix race in evtchn_fifo_unmask()
 | 0279bd8ca365 54c9de89895e o: | xen/events: add a new "late EOI" evtchn framework
 | adc67cdf742f 01263a1fabe3 .: | xen/blkback: use lateeoi irq binding
 | 322a5dc88d82 23025393dbeb .: | xen/netback: use lateeoi irq binding
 | 515827d40949 86991b6e7ea6 .: | xen/scsiback: use lateeoi irq binding
 | f2db1b870c08 c8d647a326f0 .: | xen/pvcallsback: use lateeoi irq binding
 | 8b0ac9a498d2 c2711441bc96 .: | xen/pciback: use lateeoi irq binding
 | 757d54717fae c44b849cee8c o: | xen/events: switch user event channels to lateeoi model
 | c3c580896847 7beb290caa2a o: | xen/events: use a common cpu hotplug hook for event channels
 | 7835cdf92784 e99502f76271 o: | xen/events: defer eoi in case of excessive number of events
 | f8bf3977d67c 5f7f77400ab5 o: | xen/events: block rogue events for some time

"defer eoi" should be fix for this bug.

So..we don't need to do anything here, and it will get fixed.

Best regards,
								Pavel
-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

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


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5711): https://lists.cip-project.org/g/cip-dev/message/5711
Mute This Topic: https://lists.cip-project.org/mt/77879900/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-11-02 21:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-29  2:42 [cip-dev] cip-kernel-sec Updates for Last Week of October Chen-Yu Tsai (Moxa)
2020-10-29  2:46 ` masashi.kudo
2020-11-02 11:39 ` Pavel Machek
2020-11-02 21:12   ` Pavel Machek [this message]
2020-11-05 13:49     ` Chen-Yu Tsai (Moxa)

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=20201102211225.GA2874@duo.ucw.cz \
    --to=pavel@denx.de \
    --cc=cip-dev@lists.cip-project.org \
    --cc=nobuhiro1.iwamatsu@toshiba.co.jp \
    --cc=wens@csie.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox