The complex error_msg stuff makes it difficult to track what error was
returned. For now, when we get a socket write error, throw a pr_err
immediately as well.
URL: https://tracker.ceph.com/issues/55823
Signed-off-by: Jeff Layton <jlayton@kernel.org>
if (ret < 0) {
if (ret == -EAGAIN)
continue;
- if (!con->error_msg)
+ if (!con->error_msg) {
+ pr_err("%s: socket error: %d\n", __func__, ret);
con->error_msg = "socket error on write";
+ }
fault = true;
}