Bug 1373459 - INTERNAL ERROR after fixing mishandled POLLHUP
Summary: INTERNAL ERROR after fixing mishandled POLLHUP
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: stunnel
Version: 7.3
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Tomas Mraz
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-06 10:51 UTC by Stanislav Zidek
Modified: 2018-12-05 16:33 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-12-05 16:33:08 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Stanislav Zidek 2016-09-06 10:51:08 UTC
Description of problem:
After fixing bz1170722, occurence of the problem lowered, but I am still getting the bad behaviour sometimes, newly accompanied by INTERNAL ERROR. Filing this bug to track the issue.

Version-Release number of selected component (if applicable):
stunnel-4.56-6.el7

How reproducible:
sometimes

Steps to Reproduce:
1. run  /CoreOS/stunnel/Regression/bz1170722-stunnel-loses-data-due-to-mishandled-POLLHUP (or do something equivalent - transfer a lot of data through stunnel and immediately close the connection)


Actual results:
:: [   FAIL   ] :: File '/var/tmp/tmp.ZaFmmStLcj' should contain '1000000000' 
...
:: [  BEGIN   ] :: Running 'cat stunnel.log'
...
2016.09.06 05:48:34 LOG3[16351:70367262404816]: INTERNAL ERROR: s_poll_wait returned 0, but no descriptor is ready
...
:: [   PASS   ] :: Command 'cat stunnel.log' (Expected 0, got 0)

Expected results:
* right file size
* no INTERNAL ERROR

Additional info:
See bz1170722 for details of the original issue.

Comment 1 Tomas Mraz 2018-12-05 16:33:08 UTC
There is no customer case associated with the issue, it is low severity, the fix is not known and would be with high probability non-trivial with risk of breaking other things. I am closing this.


Note You need to log in before you can comment on or make changes to this bug.