[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Bug: Failed to read initial configuration, open() syscall might be inter

From: Andriy Prystupa
Subject: Bug: Failed to read initial configuration, open() syscall might be interrupted.
Date: Mon, 10 Oct 2016 20:05:47 +0300

This was reproduced on Ubuntu 14.04 in VirtualBox. But I guess that issue exists on other distros.
It is very timing dependent issue. Using Gdb or strace easily hide it.

Our kernel has custom LSM. so open() syscall timing might be little bit changed some time. It has same effect as on slow devices I guess.

On Monday, October 10, 2016, Chet Ramey <address@hidden> wrote:
On 10/5/16 9:04 AM, Andriy Prystupa wrote:
> Hi,
> Error:
> */bash: /etc/bash.bashrc: Interrupted system call /*
> Reproduced on bash-4.4 via *gnome-terminal* or *terminator* terminal.

This is interesting.  On what version of Unix/Linux is open(2) on a regular
file from the local file system interrupted?  Traditional behavior is that
open can be interrupted when used on a `slow' device, but not otherwise.

``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    address@hidden    http://cnswww.cns.cwru.edu/~chet/


Andriy Prystupa | SW Engineer
M +38.097.330.9412  S 


reply via email to

[Prev in Thread] Current Thread [Next in Thread]