On Mon, Jan 10, 2022 at 9:19 AM Taylor Blau <me@xxxxxxxxxxxx> wrote: > > Yes, 02769437e1 appears to introduces an inadvertent use-after-free. > I'll write up the details and post the patch shortly, but an easy fix > is: Ack, that seems to fix it here for me from a _very_ cursory test. Thanks, Linus