[PATCH V3 0/1] Fix an infinite loop in nvme-tcp host driver

[Maurizio Lombardi]

I have two points I would like to discuss:

1) Are there any error codes other than -EAGAIN that deserve
   a special treatment like not starting an error recovery?

2) I remember that Hannes proposed an alternative approach to fix this.
   He suggested allowing the controller to transition directly
   from the CONNECTING to the RESETTING state.
   However, I am wary of this solution because it would allow
   the resetting code path to run concurrently with the
   connecting path, potentially introducing new race condition bugs.


Maurizio Lombardi (1):
  nvme-tcp: Prevent infinite loop if socket closes during CONNECTING
    state

 drivers/nvme/host/tcp.c | 1 +
 1 file changed, 1 insertion(+)

-- 
2.43.5