Re: fastrpc: use-after-free of fastrpc_invoke_ctx on duplicate glink responses in fastrpc_rpmsg_callback()

[bo cao]

Hi Greg,

> These two messages are not "threaded" properly, sent as 2 separate
> emails.  Is that intentional?  It breaks our tooling :(

Not intentional -- I sent them individually instead of as a series.
Sorry about that.  Resent as a properly threaded [PATCH v2 0/2]
series with git send-email (no code changes):

  0/2: https://lore.kernel.org/all/tencent_AE37F59DA9A6DAB192F6BAFD054E584FAB05@xxxxxx/
  1/2: https://lore.kernel.org/all/tencent_E9BD7808AB6A2DA5FA326D547F57D65D270A@xxxxxx/
  2/2: https://lore.kernel.org/all/tencent_C7D71E2F51C2195A0CA91A4C11D51B957708@xxxxxx/

Thanks,
bo cao