diff options
| author | Sowmini Varadhan <[email protected]> | 2017-03-31 22:56:30 +0000 |
|---|---|---|
| committer | David S. Miller <[email protected]> | 2017-04-03 02:41:00 +0000 |
| commit | e97656d03ca0cea888a0b9d382abce8233771f31 (patch) | |
| tree | 4717f3e414f1d9a36a205d0a306888be19c1cc29 /lib/memory-notifier-error-inject.c | |
| parent | sock: correctly test SOCK_TIMESTAMP in sock_recv_ts_and_drops() (diff) | |
| download | kernel-e97656d03ca0cea888a0b9d382abce8233771f31.tar.gz kernel-e97656d03ca0cea888a0b9d382abce8233771f31.zip | |
rds: tcp: allow progress of rds_conn_shutdown if the rds_connection is marked ERROR by an intervening FIN
rds_conn_shutdown() runs in workq context, and marks the rds_connection
as DISCONNECTING before quiescing Tx/Rx paths. However, after all I/O
has quiesced, we may still find the rds_connection state to be
RDS_CONN_ERROR if an intervening FIN was processed in softirq context.
This is not a fatal error: rds_conn_shutdown() should continue the
shutdown, and there is no need to log noisy messages about this event.
Signed-off-by: Sowmini Varadhan <[email protected]>
Acked-by: Santosh Shilimkar <[email protected]>
Signed-off-by: David S. Miller <[email protected]>
Diffstat (limited to 'lib/memory-notifier-error-inject.c')
0 files changed, 0 insertions, 0 deletions