Hello, Trying to understand how watch/notify works for his v2 work, Doug tried a simple test which uncovered a regression in lingering request requeue code dating back to 3.18. As it pretty much always is, a one liner is all it took. The reason it went unnoticed is we can't thrash it because of watch/notify v1 limitations and the last round of manual testing I did was around 3.16-3.17 after a bunch of fixes in that area, so only osd-requeue (as opposed to osdmap-requeue) path was stressed. While investigating it I found another problem, which probably goes all the way back to the addition of watch/notify and that is what the first patch is for. The regression itself is fixed by a revert, with the ground for it set up in the first patch. Both are marked for stable and will be backported together. Thanks, Ilya Ilya Dryomov (2): libceph: request a new osdmap if lingering request maps to no osd Revert "libceph: clear r_req_lru_item in __unregister_linger_request()" net/ceph/osd_client.c | 33 ++++++++++++++++++++------------- 1 file changed, 20 insertions(+), 13 deletions(-) -- 1.9.3 -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html