9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] recent changes
Date: Tue, 08 Dec 2020 19:29:56 -0500	[thread overview]
Message-ID: <A5DAACCF-70CD-40AE-8FBF-08B087954072@stanleylieber.com> (raw)
In-Reply-To: <BAA518A2EB38549011C76294FB6AFC86@felloff.net>

On December 8, 2020 7:24:49 PM EST, cinap_lenrek@felloff.net wrote:
>i located the issue.
>
>it can be reproduced when cpuing to another machine and
>running window -m.
>
>the problem is that OCEXEC doesnt work too tell with
>/srv files.
>
>when any program opens a /srv file with OCEXEC flag,
>it sets the close-on-exec flag on the shared channel,
>resulting in all subsequent opens (regardless of the
>flag) to have close-on-exec semantics.
>
>that happens with the $wsys channel.
>
>it is interesting as devsrv itself tries hard to
>prevent you from posting a file descriptor with the
>close-on-exec flag set. but subsequent opens can
>still poison the channel.
>
>the fixes are pushed.
>
>--
>cinap

thank you, i can confirm tonight.

sl

  reply	other threads:[~2020-12-09  0:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-08 16:01 Stanley Lieber
2020-12-08 16:08 ` [9front] " Stanley Lieber
2020-12-08 16:46   ` Eckard Brauer
2020-12-08 16:50   ` cinap_lenrek
2020-12-08 17:04     ` Stuart Morrow
2020-12-08 16:56   ` Kurt H Maier
2020-12-08 16:49 ` [9front] " ori
2020-12-08 20:08   ` cinap_lenrek
2020-12-09  0:24     ` cinap_lenrek
2020-12-09  0:29       ` Stanley Lieber [this message]
2020-12-09  9:34         ` umbraticus
2020-12-09 14:32           ` Stanley Lieber

Reply instructions:

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=A5DAACCF-70CD-40AE-8FBF-08B087954072@stanleylieber.com \
    --to=sl@stanleylieber.com \
    --cc=9front@9front.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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).