commit | a3f668d218f381ffb36a6334425ba09ef5a33b7f | [log] [tgz] |
---|---|---|
author | Michal Kazior <michal.kazior@tieto.com> | Thu Oct 30 02:22:39 2014 -0700 |
committer | Ke Dong <kedong@google.com> | Thu Oct 30 18:02:47 2014 -0700 |
tree | a3cc9c180d0a14a389f9ec0dd2bee137e53d0a14 | |
parent | eb2742cd5ae7f1abf90c8c518d11bfe2c0c1e0c0 [diff] |
Michal Kazior michal.kazior at tieto.com Fri Apr 4 07:37:42 EDT 2014 It was troublesome to iterate over peers within a sleepable context (e.g. while holding conf_mutex). This will be necessary for some upcomming changes to tx flushing. Making peer allocation and initial setup ar->conf_mutex bound instead ar->data_lock solves the problem. Change-Id: I72b815957e6e2abb52fb7d16a40e0f6fbe5b877f Signed-off-by: Michal Kazior <michal.kazior at tieto.com>