All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Ian Jackson <iwj@xenproject.org>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	Dario Faggioli <dfaggioli@suse.com>,
	Julien Grall <julien@xen.org>,
	community.manager@xenproject.org, committers@xenproject.org,
	xen-devel@lists.xenproject.org
Subject: Re: [ANNOUNCE] Xen 4.15 - call for notification/status of significant bugs
Date: Thu, 4 Feb 2021 15:30:48 +0100	[thread overview]
Message-ID: <86412e13-ed57-8625-18be-38dd7022669e@suse.com> (raw)
In-Reply-To: <24603.58528.901884.980466@mariner.uk.xensource.com>

On 04.02.2021 13:12, Ian Jackson wrote:
> OPEN ISSUES
> -----------
> 
> A. HPET/PIT issue on newer Intel systems
> [...]
> 
> B. "scheduler broken" bugs.
> 
> Information from
>   Andrew Cooper <andrew.cooper3@citrix.com>
>   Dario Faggioli <dfaggioli@suse.com>
> 
> Quoting Andrew Cooper
> | We've had 4 or 5 reports of Xen not working, and very little
> | investigation on whats going on.  Suspicion is that there might be
> | two bugs, one with smt=0 on recent AMD hardware, and one more
> | general "some workloads cause negative credit" and might or might
> | not be specific to credit2 (debugging feedback differs - also might
> | be 3 underlying issue).
> 
> I reviewed a thread about this and it is not clear to me where we are
> with this.

I'm not sure Marek's "Xen crash after S3 suspend - Xen 4.13 and newer"
falls in either of the two buckets.

> C. Fallout from MSR handling behavioral change.
> 
> Information from
>   Jan Beulich <jbeulich@suse.com>
> 
> I am lacking an extended desxcription of this.  What are the bug(s),
> and what is the situation ?
> 
> 
> D. Use-after-free in the IOMMU code
> 
> Information from
>   Julien Grall <julien@xen.org>
> References
>  [PATCH for-4.15 0/4] xen/iommu: Collection of bug fixes for IOMMU teadorwn
>  <20201222154338.9459-1-julien@xen.org>
> 
> Quoting the 0/:
> | This series is a collection of bug fixes for the IOMMU teardown code.
> | All of them are candidate for 4.15 as they can either leak memory or
> | lead to host crash/host corruption.
> 
> AFAIT these patches are not yet in-tree.

(since you're continuing with E. further down)

F. The almost-XSA "x86/PV: avoid speculation abuse through guest
accessors" - the first 4 patches are needed to address the actual
issue. The next 3 patches are needed to get the tree into
consistent state again, identifier-wise. The remaining patches
can probably wait.

> CLOSED ISSUES
> =============
> 
> E. zstd support
> 
> Information from
>   Andrew Cooper <andrew.cooper3@citrix.com>
>   Jan Beulich <jbeulich@suse.com>
>   git
> 
> Needed to unbreak Fedora.  Needs support for both dom0 and domU.
> 
> AFAICT this seems to be in-tree as of 8169f82049ef
> "libxenguest: support zstd compressed kernels"

Indeed.

Jan


  parent reply	other threads:[~2021-02-04 14:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-01 15:33 [ANNOUNCE] Xen 4.15 release schedule - feature freeze now in effect Ian Jackson
2021-02-04 12:12 ` [ANNOUNCE] Xen 4.15 - call for notification/status of significant bugs Ian Jackson
2021-02-04 12:20   ` Andrew Cooper
2021-02-04 15:15     ` Ian Jackson
2021-02-04 14:20   ` Dario Faggioli
2021-02-04 15:00     ` Tamas K Lengyel
2021-02-04 18:22       ` Dario Faggioli
2021-02-04 15:12     ` Ian Jackson
2021-02-04 14:30   ` Jan Beulich [this message]
2021-02-04 15:18     ` Ian Jackson
2021-02-05 15:33   ` Jan Beulich

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=86412e13-ed57-8625-18be-38dd7022669e@suse.com \
    --to=jbeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=committers@xenproject.org \
    --cc=community.manager@xenproject.org \
    --cc=dfaggioli@suse.com \
    --cc=iwj@xenproject.org \
    --cc=julien@xen.org \
    --cc=xen-devel@lists.xenproject.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.