Bug 1599606 - lsof doesn't recognize O_CLOEXEC
Summary: lsof doesn't recognize O_CLOEXEC
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: lsof
Version: 28
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jan Rybar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-10 07:30 UTC by Joe Orton
Modified: 2019-05-28 19:05 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-28 19:05:08 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Joe Orton 2018-07-10 07:30:21 UTC
Description of problem:
lsof +fg doesn't recognize O_CLOEXEC in file flags

Version-Release number of selected component (if applicable):
lsof-4.89-9.fc28.x86_64

How reproducible:
always

Steps to Reproduce:
1. systemctl start httpd
2. lsof +fg `cat /run/httpd/httpd.pid`

Actual results:
...
httpd   5337 apache    0r      CHR              LG                1,3      0t0      26 /dev/null
httpd   5337 apache    1u     unix              RW 0x00000000d72cfc55      0t0   75877 type=STREAM
httpd   5337 apache    2w      REG         W,AP,LG              253,1    99035 2359531 /var/log/httpd/error_log
httpd   5337 apache    3u     IPv6      RW,0x80000              25908      0t0     TCP *:http (LISTEN)
httpd   5337 apache    4u     IPv6      RW,0x80000              26963      0t0     TCP *:https (LISTEN)

Expected results:
show an abbreviation rather than 0x80000 (O_CLOEXEC)

Additional info:

Comment 1 Ben Cotton 2019-05-02 21:20:28 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 barsnick 2019-05-09 13:07:34 UTC
I consider this an upstream issue, so I took the liberty of suggesting this in the upstream issue tracking:

https://github.com/lsof-org/lsof/issues/38

I also provided a potential fix there.

Comment 4 Ben Cotton 2019-05-28 19:05:08 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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