b78e763c1a
Error check of strtol is left to users of it. But some use cases of strtol in SPDK do not have enough error check yet. For example, strtol returns 0 if there were no digits at all. It should be avoided for each use case to add enough error checking for strtol. Hence spdk_strtol and spdk_strtoll do additional error checking according to the description of manual of strtol. Besides, there is no use case of negative number now, and to keep simplicity, spdk_trtol and spdk_strtoll allows only strings that is positive number or zero. As a result of this policy, callers of them only have to check if the return value is not negative. Subsequent patches will replace atoi to spdk_strtol because atoi does not have error check. Change-Id: If3d549970595e53b1141674e47710fe4dd062bc5 Signed-off-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-on: https://review.gerrithub.io/c/441626 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: wuzhouhui <wuzhouhui@kingsoft.com> Reviewed-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com> |
||
|---|---|---|
| .. | ||
| base64.c | ||
| bit_array.c | ||
| cpuset.c | ||
| crc16.c | ||
| crc32_ieee.c | ||
| crc32.c | ||
| crc32c.c | ||
| dif.c | ||
| fd.c | ||
| Makefile | ||
| strerror_tls.c | ||
| string.c | ||
| uuid.c | ||