On Mon, 28 Mar 2022 15:20:02 +0900
Yuichiro NAITO wrote:
> Thanks for the explanation.
> I understand how your patch works.
>
> I want to ask the goal of your patch.
> It seems just removing 'Address already in use' message.
> Is my guessing right?
Yes. There is nothing to do, since the
Thanks for the explanation.
I understand how your patch works.
I want to ask the goal of your patch.
It seems just removing 'Address already in use' message.
Is my guessing right?
On 3/28/22 14:01, YASUOKA Masahiko wrote:
Hi,
On Mon, 28 Mar 2022 12:12:39 +0900
Yuichiro NAITO wrote:
On
> Date: Mon, 28 Mar 2022 09:51:22 -0400
> From: Demi Marie Obenour
>
> On 3/27/22 21:45, Damien Miller wrote:
> > On Fri, 25 Mar 2022, Demi Marie Obenour wrote:
> >
> >> Linux’s netfront and blkfront drivers recently had a security
> >> vulnerability (XSA-396) that allowed a malicious backend
On 3/27/22 21:45, Damien Miller wrote:
> On Fri, 25 Mar 2022, Demi Marie Obenour wrote:
>
>> Linux’s netfront and blkfront drivers recently had a security
>> vulnerability (XSA-396) that allowed a malicious backend to potentially
>> compromise them. In follow-up audits, I found that OpenBSD’s
kqueue uses a userland data structure.
The netbsd PR is saying that the userland data structure gets corrupted,
so that the event doesn't arrive. Thus the process stops.
That PR says their kernel is not buggy, but the kqueue handling.
If they are updated on libuv, maybe they are seeing the
Omar Polo wrote:
> Hello tech,
>
> mg(1) has this tendency to leave a lot of trailing whitespaces around in
> auto-indent-mode and c-mode which I find annoying. Yes, there's
> delete-trailing-space but it works only on the current line (and not the
> whole buffer as in emacs) and one has to
On 3/28/22 10:39, Mark Kettenis wrote:
>> Date: Mon, 28 Mar 2022 09:51:22 -0400
>> From: Demi Marie Obenour
>>
>> On 3/27/22 21:45, Damien Miller wrote:
>>> On Fri, 25 Mar 2022, Demi Marie Obenour wrote:
>>>
Linux’s netfront and blkfront drivers recently had a security
vulnerability
And I simply why we don't simply delete all that code.
Demi Marie Obenour wrote:
> On 3/28/22 10:39, Mark Kettenis wrote:
> >> Date: Mon, 28 Mar 2022 09:51:22 -0400
> >> From: Demi Marie Obenour
> >>
> >> On 3/27/22 21:45, Damien Miller wrote:
> >>> On Fri, 25 Mar 2022, Demi Marie Obenour
I want to use the IA32_TSC_ADJUST MSR where available when testing TSC
synchronization. We note if it's available during CPU identification.
Can we do CPU identification earlier in cpu_hatch() and
cpu_start_secondary(), before we do the TSC sync testing?
This can wait until after release. I'm
On Mon, Mar 28, 2022 at 10:52:09PM -0500, Scott Cheloha wrote:
> I want to use the IA32_TSC_ADJUST MSR where available when testing TSC
> synchronization. We note if it's available during CPU identification.
>
> Can we do CPU identification earlier in cpu_hatch() and
> cpu_start_secondary(),
10 matches
Mail list logo