9front - general discussion about 9front
 help / color / mirror / Atom feed
From: sirjofri <sirjofri+ml-9front@sirjofri.de>
To: 9front@9front.org
Subject: Re: [9front] [Bug] Mail fails to send attachments
Date: Fri, 19 Feb 2021 23:47:43 +0000 (UTC)	[thread overview]
Message-ID: <e5d20fba-9bbb-4326-8c18-a7705a2d87c7@sirjofri.de> (raw)
In-Reply-To: <5AE9D560F742B991050C8E636061FC9E@eigenstate.org>

Hello,

I did some testing and this is what I found out:

upas/send does not fail. This is at least from what I found out using 
dtracy (no status error) and other tests. It seems only marshal fails.

Marshal doesn't always call send. If there's a pipefrom, it executes that 
instead. I tried using a minimal pipefrom (saving args and all stdin in 
file, to verify) and marshal still fails (I verified that send isn't 
called at all).

This could mean that the pipe is closed by marshal itself (by one of its 
child processes).

Marshal does fork pretty often. It even forks inside forks. I'll try to 
find out more about that tomorrow. I can imagine there's one child that 
basically closes the pipe when another child still wants to write.

I currently assume this happens somewhere in marshal.c:/^sendmail, but 
today I'm way to tired to find it.

I'll be available again tomorrow and hopefully we can find it.

sirjofri

  reply	other threads:[~2021-02-19 23:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-19 19:56 theinicke
2021-02-19 20:13 ` sirjofri
2021-02-19 20:54   ` Romano
2021-02-19 21:13   ` ori
2021-02-19 23:47     ` sirjofri [this message]
2021-02-20  0:28       ` sirjofri
2021-02-20  0:49         ` ori
2021-02-20 13:02           ` sirjofri
2021-02-19 23:27   ` ori
2021-02-20 13:16     ` [9front] [Patch] " sirjofri
2021-02-20 13:37       ` hiro
2021-02-20 14:03         ` [9front] bad headers in mail (was: Mail attachment bug) sirjofri
2021-02-20 14:10           ` hiro

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=e5d20fba-9bbb-4326-8c18-a7705a2d87c7@sirjofri.de \
    --to=sirjofri+ml-9front@sirjofri.de \
    --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).