linux-kernel - Re: [LKP] [Xen-devel] [PATCH v3 0/7] Enhance PAT init to fix Xorg crashes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <CAB=NE6Wuc9Jy=CS_bGTE20MhBX95EMnrR6TZJ0tineEEo6yRgg@mail.gmail.com>
Date:	Wed, 30 Mar 2016 13:47:26 -0700
From:	"Luis R. Rodriguez" <mcgrof@...e.com>
To:	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
Cc:	Toshi Kani <toshi.kani@....com>, lkp@...1.01.org,
	"Hao, Xudong" <xudong.hao@...el.com>,
	Paul Gortmaker <paul.gortmaker@...driver.com>,
	"H. Peter Anvin" <hpa@...or.com>, Olaf Hering <ohering@...e.de>,
	Boris Ostrovsky <boris.ostrovsky@...cle.com>,
	X86 ML <x86@...nel.org>, Robert Schweikert <rjschwei@...e.com>,
	Ingo Molnar <mingo@...nel.org>,
	xen-devel <xen-devel@...ts.xenproject.org>,
	Borislav Petkov <bp@...e.de>, elliott@....com,
	Michal Marek <mmarek@...e.cz>, Olaf Hering <olaf@...fle.de>,
	Juergen Gross <jgross@...e.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Charles Arnold <carnold@...e.com>,
	Mike Latimer <mlatimer@...e.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Lars Kurth <lars.kurth@....org>,
	Vitaly Kuznetsov <vkuznets@...hat.com>,
	Fengguang Wu <fengguang.wu@...el.com>
Subject: Re: [LKP] [Xen-devel] [PATCH v3 0/7] Enhance PAT init to fix Xorg crashes

On Wed, Mar 30, 2016 at 1:29 PM, Konrad Rzeszutek Wilk
<konrad.wilk@...cle.com> wrote:
> On Wed, Mar 30, 2016 at 01:10:29PM -0700, Luis R. Rodriguez wrote:
>
> Are you saying that you expect Xen maintainers to _NOT_ test Xen related
> patches? Especially ones they have been involved with?

Of course not, I'm saying we have a bottleneck on development if we
need to wait for Xen patches to be tested, and we can do better if we
had 0-day testing this for us. In this case it was *me* who brought up
the issue of a Xen conflict early, and later through other iterations
Toshi addressed this, given we have the technology and bandwidth to do
more testing with 0-day we should not have to count on me or others to
do the proactive review to ensure there is no Xen conflict, or on
Boris for final confirmation. Its a nobrainer the value of integration
of Xen with 0-day.

>> If its really trivial then you give me the impression you can help
>> with its integration. 0-day is open after all.
>
> I have no clue on how the 0-day works - hence my question. I would be more than
> happy to help once free time lines up.

Great.

  Luis