Jan,
I had sent the mail an hour after I ran the scripts (had a meeting in between).
I will look into the issue with XSA 226
On commits c7783d9c26fc191862d9883da22387340b1fab18 &
d6aad635097d901b96df650e87f04687c9fb7bd2: I have to look into why these didn’t
get picked up.
Maybe there is a bug
>>> On 12.10.17 at 19:08, wrote:
> for 4.9.1 the XSA status is
>
> XSA 226 : Some patches not applied => check
> There is an extra chunk in the tree: see xsa226.png
I see there are outdated patches for this XSA still in xsa.git,
which I've now removed.
I can't seem to be able to confirm the dif
On Fri, Oct 6, 2017 at 6:54 AM, Andrew Cooper wrote:
> On 06/10/17 14:33, Jan Beulich wrote:
>> All,
>>
>> with the goal of releasing around the end of the month, please point
>> out backport candidates you find missing from the respective staging
>> branches, but which you consider relevant. Note
Hi all,
for 4.9.1 the XSA status is
XSA 226 : Some patches not applied => check
There is an extra chunk in the tree: see xsa226.png
XSA 227 : All patches found (no need to check)
XSA 228 : All patches found (no need to check)
XSA 229 : No patch found => check
Linux only => no issue
XSA 230 : A
I will try and run the XSA scripts this week and get back to you
Lars
On 06/10/2017, 14:33, "Jan Beulich" wrote:
All,
with the goal of releasing around the end of the month, please point
out backport candidates you find missing from the respective staging
branches, but which
On 06/10/17 14:33, Jan Beulich wrote:
> All,
>
> with the goal of releasing around the end of the month, please point
> out backport candidates you find missing from the respective staging
> branches, but which you consider relevant. Note that commits
>
> 1c2ea5ee05 x86/hvm/dmop: fix EFAULT conditi
