The application can't know if AD is trustworthy or not, I think we
should do this fully in asr(3).
I'll send a diff to tech@ that implements glibc's trust-ad
( https://gnutoolchain-gerrit.osci.io/r/c/glibc/+/461 )
On 2021-11-18 08:13 +01, Otto Moerbeek wrote:
> Hi,
>
> And here a sketch of the AD
On Sat, Nov 20 2021, Florian Obser wrote:
> The application can't know if AD is trustworthy or not, I think we
> should do this fully in asr(3).
> I'll send a diff to tech@ that implements glibc's trust-ad
> ( https://gnutoolchain-gerrit.osci.io/r/c/glibc/+/461 )
So is it time to reconsider this
On 2021-11-20 15:01 +01, Jeremie Courreges-Anglas wrote:
> On Sat, Nov 20 2021, Florian Obser wrote:
>> The application can't know if AD is trustworthy or not, I think we
>> should do this fully in asr(3).
>> I'll send a diff to tech@ that implements glibc's trust-ad
>> ( https://gnutoolchain-ger
Hi,
Regress found an data_access_fault on sparc64 pfctl
START sys/net/pf_table2021-11-20T19:26:58Z
rm -f a.out [Ee]rrs mklog *.core y.tab.h stamp-*
hit
pfctl -qt __regress_tbl -T add -f /usr/src/regress/sys/net/pf_table/table.in
Timeout, server ot21 not responding.
On 2021-11-18 6:25 p.m., Ted Bullock wrote:
> On 2021-11-15 2:41 p.m., Ted Bullock wrote:
>> On 2021-11-15 2:21 p.m., Theo de Raadt wrote:
>>> I do want fchmod for random reuse on most sparc64 machines. But if
>>> OFW "write"
>>> support isn't working on some machines, we should nop it out. Lucki
Philip Guenther writes:
> On Wed, 17 Nov 2021, Josh Grosse wrote:
> ...
>> vmm_handle_cpuid: function 0x0a (arch. perf mon) not supported
>> vmx_handle_cr: mov to cr0 @ 100149e, data=0x80010031
>> vmx_handle_wrmsr: wrmsr exit, msr=0x8b, discarding data written from
>> guest=0x0:0x0
>> vmx_hand
On Sat, 20 Nov 2021, Dave Voutila wrote:
> Philip Guenther writes:
>
> > On Wed, 17 Nov 2021, Josh Grosse wrote:
> > ...
> >> vmm_handle_cpuid: function 0x0a (arch. perf mon) not supported
> >> vmx_handle_cr: mov to cr0 @ 100149e, data=0x80010031
> >> vmx_handle_wrmsr: wrmsr exit, msr=0x8b, disca
On Sat, Nov 20, 2021 at 06:10:58PM -0500, Dave Voutila wrote:
> To me the below is the fix to the actual issue: not properly sending
> guest state back to vmd so it can provide the correct state (updated or
> not) when re-running the vcpu. I'm going to share with tech@ with pretty
> much the same w
