diff options
author | Arnd Bergmann <arnd@arndb.de> | 2016-06-17 17:33:10 +0200 |
---|---|---|
committer | Shaohua Li <shli@fb.com> | 2016-07-19 11:00:47 -0700 |
commit | 0e3ef49eda5bae3aa75aa8c0276411bf0f27e03a (patch) | |
tree | 7c4a99c0ef5930b3380aa01bf754066d11b0ab2a /drivers/md/md.h | |
parent | d787be4092e27728cb4c012bee9762098ef3c662 (diff) |
md: use seconds granularity for error logging
The md code stores the exact time of the last error in the
last_read_error variable using a timespec structure. It only
ever uses the seconds portion of that though, so we can
use a scalar for it.
There won't be an overflow in 2038 here, because it already
used monotonic time and 32-bit is enough for that, but I've
decided to use time64_t for consistency in the conversion.
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Shaohua Li <shli@fb.com>
Diffstat (limited to 'drivers/md/md.h')
-rw-r--r-- | drivers/md/md.h | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/md/md.h b/drivers/md/md.h index dc65ca65b26e..fd56cfd8c368 100644 --- a/drivers/md/md.h +++ b/drivers/md/md.h @@ -99,7 +99,7 @@ struct md_rdev { atomic_t read_errors; /* number of consecutive read errors that * we have tried to ignore. */ - struct timespec last_read_error; /* monotonic time since our + time64_t last_read_error; /* monotonic time since our * last read error */ atomic_t corrected_errors; /* number of corrected read errors, |