@Jeremy: the osbrick-leak patch addresses some possible corner cases, but is too risky to backport as it may cause regressions. Our current thinking is that it should be worked on in public as a patch to master after this issue has been made public, and can go through the normal review and CI process. (To answer your question, it wasn't supplanted by the osbrick-fc patch, it is a child of that patch.)
@Jeremy: the osbrick-leak patch addresses some possible corner cases, but is too risky to backport as it may cause regressions. Our current thinking is that it should be worked on in public as a patch to master after this issue has been made public, and can go through the normal review and CI process. (To answer your question, it wasn't supplanted by the osbrick-fc patch, it is a child of that patch.)