From: Andrew Cooper <Andrew.Cooper3@citrix.com>
To: Jan Beulich <jbeulich@suse.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: George Dunlap <George.Dunlap@citrix.com>,
Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>,
Anthony Perard <anthony.perard@citrix.com>,
Julien Grall <julien@xen.org>
Subject: Re: preparations for 4.16.1
Date: Thu, 10 Mar 2022 10:20:09 +0000 [thread overview]
Message-ID: <41020867-eaa4-839c-3380-00bd91c5299b@citrix.com> (raw)
In-Reply-To: <6f8ccbb3-d384-bedd-8fb2-18aab570b588@suse.com>
On 10/03/2022 09:01, Jan Beulich wrote:
> On 10.03.2022 09:57, Jan Beulich wrote:
>> Please point out backports you find missing from the respective staging
>> branch, but which you consider relevant. One I have queued already, but
>> which I'd like to put in only once the pending fix to it ("x86: avoid
>> SORT_BY_INIT_PRIORITY with old GNU ld") has also landed in staging, is
>>
>> 4b7fd8153ddf x86: fold sections in final binaries
> Actually the other one I'm aware of is
>
> 7d9589239ec0 x86/CET: Fix S3 resume with shadow stacks active
>
> which Andrew promised to provide a suitable backport for.
So now XSA-398 is public, I can say what that slightly cryptically meant.
The CET S3 fix depends on one of the code rearrangements introduced in
the CET-IBT work. We were intending to have CET-IBT backported for the
tuesday embargo (didn't go to plan), after which the S3 fix would be a
trivial backport to 4.14 and later.
~Andrew
next prev parent reply other threads:[~2022-03-10 10:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 8:57 preparations for 4.16.1 Jan Beulich
2022-03-10 9:01 ` Jan Beulich
2022-03-10 10:20 ` Andrew Cooper [this message]
2022-03-10 10:35 ` Jan Beulich
2022-03-10 11:14 ` Andrew Cooper
2022-03-10 11:54 ` Jan Beulich
2022-03-10 9:04 ` Julien Grall
2022-03-10 10:02 ` Bertrand Marquis
2022-03-10 10:04 ` Bertrand Marquis
2022-03-10 11:06 ` Julien Grall
2022-03-10 17:52 ` Stefano Stabellini
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=41020867-eaa4-839c-3380-00bd91c5299b@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=George.Dunlap@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=sstabellini@kernel.org \
--cc=wl@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.