On 03/01/2017 02:07 AM, Shaohua Li wrote:
On Fri, Feb 24, 2017 at 11:15:15AM +0800, Guoqing Jiang wrote:
lock_token is called from either lock_comm or
metadata_update_start, if we look back more for
the call chain, some of them are called with the
reconfig_mutex held while a few of them don't.
Specifically, resync_info_update is mostly called
without the protection of reconfig_mutex. But
resync_finish calls resync_info_update within
the mutex.
We make the change to lock_token since we need
to use synchronous way to handle METADATA_UPDATED
message in latter patch.
please merge this to the patch which uses the new paramter
NP, though I think it is easy for review.
Thanks,
Guoqing
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
