Subject: Re: [9front] fix race condition on writes to #v/vgactl
Date: Wed, 17 Aug 2022 22:23:08 -0400 [thread overview]
Message-ID: <614F45799921E978382B1562E32B1F75@eigenstate.org> (raw)
> You're absolutely right. Here's another attempt; the code is a mess,
> but I'm not up for refactoring it all right now.
> What do you think?
looks ok to me.
Though, I wonder if we can just simplify by taking the lock on
entry, and release it on return; I don't think that any of
these operations happen often, so we don't need to be fine
next prev parent reply other threads:[~2022-08-18 2:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 6:12 qwx
2022-08-16 20:44 ` qwx
2022-08-16 20:51 ` Jacob Moody
2022-08-16 23:02 ` Anthony Martin
2022-08-17 12:10 ` qwx
2022-08-17 12:17 ` ori
2022-08-17 20:21 ` qwx
2022-08-18 2:23 ` ori [this message]
2022-08-18 5:36 ` qwx
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).