* XSM denials with 4.7.0 RC1
@ 2016-05-04 13:52 Doug Goldstein
2016-05-04 13:58 ` Jan Beulich
` (2 more replies)
0 siblings, 3 replies; 9+ messages in thread
From: Doug Goldstein @ 2016-05-04 13:52 UTC (permalink / raw)
To: xen-devel@lists.xen.org
[-- Attachment #1.1.1: Type: text/plain, Size: 1433 bytes --]
Hi all,
Sometime after d4cd5a205973171475b8c63bc250c2803e0f51fa, I get the
following denials for any domU that attempts to run "xl". In my
situation my domU needs to run "xl devd" because its a driver domain.
(XEN) avc: denied { xen_extraversion } for domid=1
scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
tclass=version
(XEN) avc: denied { xen_extraversion } for domid=1
scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
tclass=version
(XEN) avc: denied { xen_compile_info } for domid=1
scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
tclass=version
(XEN) avc: denied { xen_capabilities } for domid=1
scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
tclass=version
(XEN) avc: denied { xen_changeset } for domid=1
scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
tclass=version
(XEN) avc: denied { xen_pagesize } for domid=1
scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
tclass=version
(XEN) avc: denied { xen_commandline } for domid=1
scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
tclass=version
(XEN) avc: denied { xen_build_id } for domid=1
scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
tclass=version
I'm guessing a changed happened to xl so that it queries the version
info everytime it is run.
--
Doug Goldstein
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 959 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: XSM denials with 4.7.0 RC1
2016-05-04 13:52 XSM denials with 4.7.0 RC1 Doug Goldstein
@ 2016-05-04 13:58 ` Jan Beulich
2016-05-04 14:00 ` Doug Goldstein
2016-05-04 14:05 ` Wei Liu
2016-05-04 17:20 ` Daniel De Graaf
2 siblings, 1 reply; 9+ messages in thread
From: Jan Beulich @ 2016-05-04 13:58 UTC (permalink / raw)
To: Doug Goldstein; +Cc: xen-devel@lists.xen.org
>>> On 04.05.16 at 15:52, <cardoe@cardoe.com> wrote:
> Hi all,
>
> Sometime after d4cd5a205973171475b8c63bc250c2803e0f51fa, I get the
> following denials for any domU that attempts to run "xl". In my
> situation my domU needs to run "xl devd" because its a driver domain.
>
> (XEN) avc: denied { xen_extraversion } for domid=1
> scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
> tclass=version
> (XEN) avc: denied { xen_extraversion } for domid=1
> scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
> tclass=version
> (XEN) avc: denied { xen_compile_info } for domid=1
> scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
> tclass=version
> (XEN) avc: denied { xen_capabilities } for domid=1
> scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
> tclass=version
> (XEN) avc: denied { xen_changeset } for domid=1
> scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
> tclass=version
> (XEN) avc: denied { xen_pagesize } for domid=1
> scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
> tclass=version
> (XEN) avc: denied { xen_commandline } for domid=1
> scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
> tclass=version
> (XEN) avc: denied { xen_build_id } for domid=1
> scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
> tclass=version
>
> I'm guessing a changed happened to xl so that it queries the version
> info everytime it is run.
Perhaps it did that always, and it has become a problem only
because of the XSM check which the version hypercall obtained
recently?
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: XSM denials with 4.7.0 RC1
2016-05-04 13:58 ` Jan Beulich
@ 2016-05-04 14:00 ` Doug Goldstein
0 siblings, 0 replies; 9+ messages in thread
From: Doug Goldstein @ 2016-05-04 14:00 UTC (permalink / raw)
To: Jan Beulich; +Cc: xen-devel@lists.xen.org
[-- Attachment #1.1.1: Type: text/plain, Size: 2008 bytes --]
On 5/4/16 8:58 AM, Jan Beulich wrote:
>>>> On 04.05.16 at 15:52, <cardoe@cardoe.com> wrote:
>> Hi all,
>>
>> Sometime after d4cd5a205973171475b8c63bc250c2803e0f51fa, I get the
>> following denials for any domU that attempts to run "xl". In my
>> situation my domU needs to run "xl devd" because its a driver domain.
>>
>> (XEN) avc: denied { xen_extraversion } for domid=1
>> scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
>> tclass=version
>> (XEN) avc: denied { xen_extraversion } for domid=1
>> scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
>> tclass=version
>> (XEN) avc: denied { xen_compile_info } for domid=1
>> scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
>> tclass=version
>> (XEN) avc: denied { xen_capabilities } for domid=1
>> scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
>> tclass=version
>> (XEN) avc: denied { xen_changeset } for domid=1
>> scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
>> tclass=version
>> (XEN) avc: denied { xen_pagesize } for domid=1
>> scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
>> tclass=version
>> (XEN) avc: denied { xen_commandline } for domid=1
>> scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
>> tclass=version
>> (XEN) avc: denied { xen_build_id } for domid=1
>> scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
>> tclass=version
>>
>> I'm guessing a changed happened to xl so that it queries the version
>> info everytime it is run.
>
> Perhaps it did that always, and it has become a problem only
> because of the XSM check which the version hypercall obtained
> recently?
>
> Jan
>
That would do it as well, thank you. I knew there was a change in this
code path recently and I remembered Konrad was active in it so I CC'd him.
If no one else proposes a change I'll look at making a patch tomorrow.
--
Doug Goldstein
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 959 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: XSM denials with 4.7.0 RC1
2016-05-04 13:52 XSM denials with 4.7.0 RC1 Doug Goldstein
2016-05-04 13:58 ` Jan Beulich
@ 2016-05-04 14:05 ` Wei Liu
2016-05-04 15:33 ` Konrad Rzeszutek Wilk
2016-05-04 17:20 ` Daniel De Graaf
2 siblings, 1 reply; 9+ messages in thread
From: Wei Liu @ 2016-05-04 14:05 UTC (permalink / raw)
To: Doug Goldstein; +Cc: ross.lagerwall, Wei Liu, xen-devel@lists.xen.org
CC Konrad and Ross
On Wed, May 04, 2016 at 08:52:24AM -0500, Doug Goldstein wrote:
> Hi all,
>
> Sometime after d4cd5a205973171475b8c63bc250c2803e0f51fa, I get the
> following denials for any domU that attempts to run "xl". In my
> situation my domU needs to run "xl devd" because its a driver domain.
>
> (XEN) avc: denied { xen_extraversion } for domid=1
> scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
> tclass=version
> (XEN) avc: denied { xen_extraversion } for domid=1
> scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
> tclass=version
> (XEN) avc: denied { xen_compile_info } for domid=1
> scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
> tclass=version
> (XEN) avc: denied { xen_capabilities } for domid=1
> scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
> tclass=version
> (XEN) avc: denied { xen_changeset } for domid=1
> scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
> tclass=version
> (XEN) avc: denied { xen_pagesize } for domid=1
> scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
> tclass=version
> (XEN) avc: denied { xen_commandline } for domid=1
> scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
> tclass=version
> (XEN) avc: denied { xen_build_id } for domid=1
> scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
> tclass=version
>
> I'm guessing a changed happened to xl so that it queries the version
> info everytime it is run.
>
I think the root cause is that we have now altered xen_version hypercall
for xsplice.
We might need to update the hook, the default policy (assuming that's
what you use) or both.
Wei.
> --
> Doug Goldstein
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: XSM denials with 4.7.0 RC1
2016-05-04 14:05 ` Wei Liu
@ 2016-05-04 15:33 ` Konrad Rzeszutek Wilk
0 siblings, 0 replies; 9+ messages in thread
From: Konrad Rzeszutek Wilk @ 2016-05-04 15:33 UTC (permalink / raw)
To: Wei Liu; +Cc: ross.lagerwall, Doug Goldstein, xen-devel@lists.xen.org
On Wed, May 04, 2016 at 03:05:38PM +0100, Wei Liu wrote:
> CC Konrad and Ross
>
> On Wed, May 04, 2016 at 08:52:24AM -0500, Doug Goldstein wrote:
> > Hi all,
> >
> > Sometime after d4cd5a205973171475b8c63bc250c2803e0f51fa, I get the
> > following denials for any domU that attempts to run "xl". In my
> > situation my domU needs to run "xl devd" because its a driver domain.
> >
> > (XEN) avc: denied { xen_extraversion } for domid=1
> > scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
> > tclass=version
> > (XEN) avc: denied { xen_extraversion } for domid=1
> > scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
> > tclass=version
> > (XEN) avc: denied { xen_compile_info } for domid=1
> > scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
> > tclass=version
> > (XEN) avc: denied { xen_capabilities } for domid=1
> > scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
> > tclass=version
> > (XEN) avc: denied { xen_changeset } for domid=1
> > scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
> > tclass=version
> > (XEN) avc: denied { xen_pagesize } for domid=1
> > scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
> > tclass=version
> > (XEN) avc: denied { xen_commandline } for domid=1
> > scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
> > tclass=version
> > (XEN) avc: denied { xen_build_id } for domid=1
> > scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
> > tclass=version
> >
> > I'm guessing a changed happened to xl so that it queries the version
> > info everytime it is run.
> >
>
> I think the root cause is that we have now altered xen_version hypercall
> for xsplice.
>
> We might need to update the hook, the default policy (assuming that's
> what you use) or both.
The policy:
# For normal guests all possible except XENVER_commandline.
allow domain_type xen_t:version {
xen_extraversion xen_compile_info xen_capabilities
xen_changeset xen_pagesize xen_guest_handle
};
So not sure why you are seeing those. Did you rebuild your policy against
4.7.0-1rc?
The xen_build_id and xen_commandline should definitly error out per:
a2fc8d514df2b38c310d4f4432fe06520b0769ed
Author: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Date: Fri Mar 11 21:40:43 2016 -0500
xsm/xen_version: Add XSM for most of xen_version hypercall
The subop for XENVER_commandline is now a priviliged operation.
To not break guests we still return an string - but it is
just '<denied>\0'.
And the XSM checks would trigger for XENVER_commandline - it just that
instead of -EPERM being returned we return '<denied>\0'.
Is that not the case?
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: XSM denials with 4.7.0 RC1
2016-05-04 13:52 XSM denials with 4.7.0 RC1 Doug Goldstein
2016-05-04 13:58 ` Jan Beulich
2016-05-04 14:05 ` Wei Liu
@ 2016-05-04 17:20 ` Daniel De Graaf
2016-05-04 19:35 ` Doug Goldstein
2 siblings, 1 reply; 9+ messages in thread
From: Daniel De Graaf @ 2016-05-04 17:20 UTC (permalink / raw)
To: Doug Goldstein, xen-devel@lists.xen.org
On 05/04/2016 09:52 AM, Doug Goldstein wrote:
> Hi all,
>
> Sometime after d4cd5a205973171475b8c63bc250c2803e0f51fa, I get the
> following denials for any domU that attempts to run "xl". In my
> situation my domU needs to run "xl devd" because its a driver domain.
>
> (XEN) avc: denied { xen_extraversion } for domid=1
> scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
> tclass=version
> (XEN) avc: denied { xen_extraversion } for domid=1
> scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
> tclass=version
> (XEN) avc: denied { xen_compile_info } for domid=1
> scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
> tclass=version
> (XEN) avc: denied { xen_capabilities } for domid=1
> scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
> tclass=version
> (XEN) avc: denied { xen_changeset } for domid=1
> scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
> tclass=version
> (XEN) avc: denied { xen_pagesize } for domid=1
> scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
> tclass=version
These 6 denials should not happen with the policy in 4.7.0-rc1; are
you using an older policy?
> (XEN) avc: denied { xen_commandline } for domid=1
> scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
> tclass=version
> (XEN) avc: denied { xen_build_id } for domid=1
> scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
> tclass=version
If these show up for domUs in normal operation (and I think using
"xl devd" probably qualifies for that), then they probably need
dontaudit rules.
--
Daniel De Graaf
National Security Agency
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: XSM denials with 4.7.0 RC1
2016-05-04 17:20 ` Daniel De Graaf
@ 2016-05-04 19:35 ` Doug Goldstein
2016-05-04 19:39 ` Konrad Rzeszutek Wilk
0 siblings, 1 reply; 9+ messages in thread
From: Doug Goldstein @ 2016-05-04 19:35 UTC (permalink / raw)
To: Daniel De Graaf, xen-devel@lists.xen.org
[-- Attachment #1.1.1: Type: text/plain, Size: 2130 bytes --]
On 5/4/16 12:20 PM, Daniel De Graaf wrote:
> On 05/04/2016 09:52 AM, Doug Goldstein wrote:
>> Hi all,
>>
>> Sometime after d4cd5a205973171475b8c63bc250c2803e0f51fa, I get the
>> following denials for any domU that attempts to run "xl". In my
>> situation my domU needs to run "xl devd" because its a driver domain.
>>
>> (XEN) avc: denied { xen_extraversion } for domid=1
>> scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
>> tclass=version
>> (XEN) avc: denied { xen_extraversion } for domid=1
>> scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
>> tclass=version
>> (XEN) avc: denied { xen_compile_info } for domid=1
>> scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
>> tclass=version
>> (XEN) avc: denied { xen_capabilities } for domid=1
>> scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
>> tclass=version
>> (XEN) avc: denied { xen_changeset } for domid=1
>> scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
>> tclass=version
>> (XEN) avc: denied { xen_pagesize } for domid=1
>> scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
>> tclass=version
>
> These 6 denials should not happen with the policy in 4.7.0-rc1; are
> you using an older policy?
Well it turns out yes I was using a bad policy. I grabbed the policy
updates from master and not from 4.7.0-rc1 when I merged them with my
policy. So yes the above are incorrect and noise on my part. master
wasn't (and still isn't) at the same point that 4.7.0-rc1 was at.
>
>> (XEN) avc: denied { xen_commandline } for domid=1
>> scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
>> tclass=version
>> (XEN) avc: denied { xen_build_id } for domid=1
>> scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
>> tclass=version
>
> If these show up for domUs in normal operation (and I think using
> "xl devd" probably qualifies for that), then they probably need
> dontaudit rules.
>
These are still happening for any domD running "xl devd".
--
Doug Goldstein
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 959 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: XSM denials with 4.7.0 RC1
2016-05-04 19:35 ` Doug Goldstein
@ 2016-05-04 19:39 ` Konrad Rzeszutek Wilk
2016-05-04 19:43 ` Doug Goldstein
0 siblings, 1 reply; 9+ messages in thread
From: Konrad Rzeszutek Wilk @ 2016-05-04 19:39 UTC (permalink / raw)
To: Doug Goldstein; +Cc: Daniel De Graaf, xen-devel@lists.xen.org
>
> Well it turns out yes I was using a bad policy. I grabbed the policy
> updates from master and not from 4.7.0-rc1 when I merged them with my
> policy. So yes the above are incorrect and noise on my part. master
> wasn't (and still isn't) at the same point that 4.7.0-rc1 was at.
>
> >
> >> (XEN) avc: denied { xen_commandline } for domid=1
> >> scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
> >> tclass=version
> >> (XEN) avc: denied { xen_build_id } for domid=1
> >> scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
> >> tclass=version
> >
> > If these show up for domUs in normal operation (and I think using
> > "xl devd" probably qualifies for that), then they probably need
> > dontaudit rules.
> >
>
> These are still happening for any domD running "xl devd".
Is 'domD' not part of domain_type?
As in the policy has:
allow domain_type xen_t:version {
xen_extraversion xen_compile_info xen_capabilities
xen_changeset xen_pagesize xen_guest_handle
};
Is domD under a different type? In which case it sounds as if you
are using a non-default XSM policy?
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: XSM denials with 4.7.0 RC1
2016-05-04 19:39 ` Konrad Rzeszutek Wilk
@ 2016-05-04 19:43 ` Doug Goldstein
0 siblings, 0 replies; 9+ messages in thread
From: Doug Goldstein @ 2016-05-04 19:43 UTC (permalink / raw)
To: Konrad Rzeszutek Wilk; +Cc: Daniel De Graaf, xen-devel@lists.xen.org
[-- Attachment #1.1.1: Type: text/plain, Size: 1566 bytes --]
On 5/4/16 2:39 PM, Konrad Rzeszutek Wilk wrote:
>>
>> Well it turns out yes I was using a bad policy. I grabbed the policy
>> updates from master and not from 4.7.0-rc1 when I merged them with my
>> policy. So yes the above are incorrect and noise on my part. master
>> wasn't (and still isn't) at the same point that 4.7.0-rc1 was at.
>>
>>>
>>>> (XEN) avc: denied { xen_commandline } for domid=1
>>>> scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
>>>> tclass=version
>>>> (XEN) avc: denied { xen_build_id } for domid=1
>>>> scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
>>>> tclass=version
>>>
>>> If these show up for domUs in normal operation (and I think using
>>> "xl devd" probably qualifies for that), then they probably need
>>> dontaudit rules.
>>>
>>
>> These are still happening for any domD running "xl devd".
>
> Is 'domD' not part of domain_type?
>
> As in the policy has:
>
> allow domain_type xen_t:version {
> xen_extraversion xen_compile_info xen_capabilities
> xen_changeset xen_pagesize xen_guest_handle
> };
>
> Is domD under a different type? In which case it sounds as if you
> are using a non-default XSM policy?
>
I'm calling it domD (since I'm passing a device into it) but its a domU.
Ignore my wording. I've got a few extra allows at the bottom of the
default policy to allow a PCI device to be passed in.
--
Doug Goldstein
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 959 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2016-05-04 19:43 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-05-04 13:52 XSM denials with 4.7.0 RC1 Doug Goldstein
2016-05-04 13:58 ` Jan Beulich
2016-05-04 14:00 ` Doug Goldstein
2016-05-04 14:05 ` Wei Liu
2016-05-04 15:33 ` Konrad Rzeszutek Wilk
2016-05-04 17:20 ` Daniel De Graaf
2016-05-04 19:35 ` Doug Goldstein
2016-05-04 19:39 ` Konrad Rzeszutek Wilk
2016-05-04 19:43 ` Doug Goldstein
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.