Bug 2230213 - Please enable CONFIG_INET_DIAG_DESTROY kernel option
Summary: Please enable CONFIG_INET_DIAG_DESTROY kernel option
Keywords:
Status: MODIFIED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: kernel
Version: 8.8
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Andrea Claudi
QA Contact: Mingyu Shi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-09 01:50 UTC by Martin Schwenke
Modified: 2023-08-17 12:02 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gitlab redhat/rhel/src/kernel rhel-8 merge_requests 5210 0 None None None 2023-08-14 17:23:24 UTC
Red Hat Issue Tracker RHELPLAN-164943 0 None None None 2023-08-09 01:51:06 UTC

Description Martin Schwenke 2023-08-09 01:50:24 UTC
Description of problem:

The ss command's -K | --kill option can be used to forcibly close sockets.  This is very useful for scripting failover in a high-availability setting.  In particular, it can be used to reset the server end of TCP connections so failback will work if a client reconnects using the same source socket.

Other Linux distributions such as Debian and Ubuntu enable this kernel option.

Version-Release number of selected component (if applicable):

all

How reproducible:

This is wishlist, so always.


Steps to Reproduce:
1. ssh 127.0.0.1
2. Try "ss -tanH --kill  state established src 127.0.0.1:22"

If this worked then it would print the connection(s) that were closed.  Can see connection(s) still exist with above command but without --kill option.

Actual results:

Does not close connection(s) and print details


Expected results:

Closes connection(s) and prints details

Additional info:

Kernel config says

# CONFIG_INET_DIAG_DESTROY is not set

This is the case on RHEL 8 and 9.


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