Project

General

Profile

Actions

Bug #14240

open

SO_SNDTIMEO / SO_RCVTIMEO with no effect on AF_UNIX / SOCK_STREAM

Added by Nils Goroll 18 days ago. Updated 16 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Difficulty:
Medium
Tags:
Gerrit CR:

Description

Ref

It seems that the timeout socket options have no effect as of SmartOS 20190214T002809Z. I am opening this issue because I found no changes in the tree looking for (?i)SNDTIMEO|RCVTIMEO since #5898 , which I presume was for SOCK_DGRAM .

The gist above contains a trivial example based on the code from unix(7) :

  • In the server, setsockopt(SO_RCVTIMEO) for 0.1s timeout is added before read() .
  • In the client, a sleep(1) is inserted before write() .

This makes the server fail immediately on Linux (as expected), but not on SmartOS.

Actions #1

Updated by Robert Mustacchi 16 days ago

  • Project changed from site to illumos gate
Actions #2

Updated by Dan McDonald 16 days ago

By saying "no effect as of SmartOS 20190214T002809Z", do you mean the timeouts worked properly in older SmartOS revisions? Or do you mean that you tried this on 20190214T002809Z and you know it failed there and/or later?

I ask to see if it's a relatively recently-introduced regression or if it was perhaps always a bug?

Actions

Also available in: Atom PDF