Here's the culprit IMHO:
ea68b9372319fd0bab40856db26528d36359102e
----
rgw: don't allow multiple writers to same multiobject part
Fixes: #8269
Backport: firefly, dumpling
A client might need to retry a multipart part write. The original thread
might race with the new one, trying to clean up after it, clobbering the
part's data.
The fix is to detect whether an original part already existed, and if so
use a different part name for it.
Signed-off-by: Yehuda Sadeh <yeh...@inktank.com>
(cherry picked from commit bd8e026f88b812cc70caf6232c247844df5d99bf)
----
This is the first commit that, if you apply b300318113b162522759d4794b1cfa
3d1d9398e4 over it, will cause a segfault.
Cheers,
Sylvain
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
