{"push_id":1778141944,"size":1,"distinct_size":1,"ref":"refs/heads/futures2","head":"27f038c5a51a97a3c067a2ede7fc2a0a9dfa22f4","before":"784493e33df300a18187d8467b48c35f6e58221f","commits":[{"sha":"27f038c5a51a97a3c067a2ede7fc2a0a9dfa22f4","author":{"name":"Jim Garlick","email":"68f7fa2610b0dc79dc156867f188832fba6e3cfc@gmail.com"},"message":"libflux/dispatch: tighten fastpath response match\n\nProblem: dispatch fastpath does not check if a response is\nin the correct \"matchtag domain\", so a flux module performing\na routing function like the connector-local module, might\ninadvertantly confuse on of its RPC responses for one intended\nfor a connected user.\n\nThe only RPC that I know of that fits this profile is the\nsubscribe/unsubscribe RPCs made from connector-local to the\nbroker.  With changes to flux_rpc() to use futures, the\nmatching code switched from flux_recv() with a struct flux_match\nto the dispatcher, so while this is an old bug, its manifestantion\nis new with futures.","distinct":true,"url":"https://api.github.com/repos/garlick/flux-core/commits/27f038c5a51a97a3c067a2ede7fc2a0a9dfa22f4"}]}
{"actor":{"display_login":"garlick"}}