git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Santiago Torres Arias <santiago@nyu.edu>
To: "R. Diez" <rdiez@neanderfunk.de>
Cc: git@vger.kernel.org
Subject: Re: Interrupted system call
Date: Wed, 1 Jul 2020 10:22:05 -0400	[thread overview]
Message-ID: <20200701142205.3gwltulmkrd6iljk@LykOS.localdomain> (raw)
In-Reply-To: <c8061cce-71e4-17bd-a56a-a5fed93804da@neanderfunk.de>

[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]

Hi, 

> Nevertheless, I am surprised to get such an "Interrupted system call" from
> Git. A long time ago I learnt that it is OK for many syscalls to get
> interrupted, so you have to loop around them. See here for more information:
> 
> https://urldefense.proofpoint.com/v2/url?u=http-3A__250bpm.com_blog-3A12&d=DwICaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=yZMPY-APGKyVIX7HgQFZJA&m=JwtG1XJ8aqvchYKsbjW23-PqEl4qm4xuOrYLaF8MOK4&s=k58MMdPdIRPl0kpuTohwZo_3GbW7elvojU1wjTil2GY&e=
> 
> As a result, users should never actually get an "Interrupted system call"
> error from any software, at least when no sockets or non-blocking I/O is
> involved.

I'm not sure if you can blame git right away (it could be an underlying
library), and I'm also not convinced that "interrupted system call" is
an error that should never exist for users (error handling is generally
very nuanced).

I'd advice to use GIT_TRACE_FSMONITOR or just GIT_TRACE to figure out
what component is the last one in place before things failed. You can
read about these on the manpage on the "other" subsection of the
"ENVIRONMENT VARIABLES" section.

I hope this helps!
-Santiago

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-07-01 14:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <14b3d372-f3fe-c06c-dd56-1d9799a12632@yahoo.de>
2020-07-01  9:43 ` Interrupted system call R. Diez
2020-07-01 14:22   ` Santiago Torres Arias [this message]
2020-07-01 16:21   ` Jeff King
2020-07-02  7:07     ` R. Diez
2020-07-15  9:38       ` Jeff King
2020-07-15 16:06         ` Chris Torek
2020-07-12  8:41     ` R. Diez

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=20200701142205.3gwltulmkrd6iljk@LykOS.localdomain \
    --to=santiago@nyu.edu \
    --cc=git@vger.kernel.org \
    --cc=rdiez@neanderfunk.de \
    /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).