summaryrefslogtreecommitdiff
path: root/drivers/clocksource/clps711x-timer.c
diff options
context:
space:
mode:
authorHou Pu <houpu@bytedance.com>2020-08-10 15:00:44 +0300
committerJens Axboe <axboe@kernel.dk>2020-08-26 18:08:49 +0300
commitacb19e17c5134dd78668c429ecba5b481f038e6a (patch)
tree9d6ec5a213efd4479562c803cd13728287282484 /drivers/clocksource/clps711x-timer.c
parent2d62e6b038e729c3e4bfbfcfbd44800ef0883680 (diff)
downloadlinux-acb19e17c5134dd78668c429ecba5b481f038e6a.tar.xz
nbd: restore default timeout when setting it to zero
If we configured io timeout of nbd0 to 100s. Later after we finished using it, we configured nbd0 again and set the io timeout to 0. We expect it would timeout after 30 seconds and keep retry. But in fact we could not change the timeout when we set it to 0. the timeout is still the original 100s. So change the timeout to default 30s when we set it to zero. It also behaves same as commit 2da22da57348 ("nbd: fix zero cmd timeout handling v2"). It becomes more important if we were reconfigure a nbd device and the io timeout it set to zero. Because it could take 30s to detect the new socket and thus io could be completed more quickly compared to 100s. Signed-off-by: Hou Pu <houpu@bytedance.com> Reviewed-by: Josef Bacik <josef@toxicpanda.com> Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'drivers/clocksource/clps711x-timer.c')
0 files changed, 0 insertions, 0 deletions