summaryrefslogtreecommitdiffstats
path: root/arch/h8300
diff options
context:
space:
mode:
authorZhengyuan Liu <liuzhengyuan@kylinos.cn>2016-12-04 16:49:44 +0800
committerShaohua Li <shli@fb.com>2016-12-05 17:11:02 -0800
commit3d7e7e1d9db048bc6c1503bca9c82193450fc476 (patch)
treea9f0729aae90a6974822263329fac7e33e6f7852 /arch/h8300
parent43b9674832cc41ad0ad7b7e2ec397e47dcd5f6c3 (diff)
downloadlinux-3d7e7e1d9db048bc6c1503bca9c82193450fc476.tar.bz2
md/r5cache: do r5c_update_log_state after log recovery
We should update log state after we did a log recovery, current completion may get wrong log state since log->log_start wasn't initalized until we called r5l_recovery_log. At log recovery stage, no lock needed as there is no race conditon. next_checkpoint field will be initialized in r5l_recovery_log too. Signed-off-by: Zhengyuan Liu <liuzhengyuan@kylinos.cn> Signed-off-by: Shaohua Li <shli@fb.com>
Diffstat (limited to 'arch/h8300')
0 files changed, 0 insertions, 0 deletions