hjwsm1989 opened a new pull request, #3359:
URL: https://github.com/apache/brpc/pull/3359

   ### What problem does this PR solve?
   
   Issue Number: #3358
   
   Problem Summary:
   This fixes a `selective_channel` race where a late `SubDone::Run()` may 
re-enter
   retry/backup after the main RPC has already entered `EndRPC()`.
   
   The crash report in #3358 shows that a late sub-call callback can still flow 
into:
   
   - `Controller::OnVersionedRPCReturned()`
   - `Controller::IssueRPC()`
   - `schan::Sender::IssueRPC()`
   
   after the main controller has already started tearing down its state.
   
   That leaves `selective_channel` vulnerable to retrying on partially torn-down
   state, including the previously observed null balancer path.
   
   ### What is changed and the side effects?
   
   Changed:
   - mark the controller as "ending RPC" at the beginning of `EndRPC()`
   - ignore late `SubDone` callbacks once the main RPC is already ending
   - keep a defensive null check in `schan::Sender::IssueRPC()`
   
   This keeps the retry/backup state machine from re-entering after teardown has
   started, and also preserves a hard guard at the `selective_channel` boundary.
   
   Test:
   Added a regression test that:
   
   - uses `SelectiveChannel`
   - enables backup request and retry
   - lets the main RPC time out first
   - lets delayed sub-calls finish later
   
   This reproduces the late callback window and verifies it no longer re-enters
   retry/backup after timeout.
   
   Also re-ran related selective/backup request tests.
   
   Side effects:
   - Performance effects:
   
   - Breaking backward compatibility: 
   
   ---
   ### Check List:
   - Please make sure your changes are compilable.
   - When providing us with a new feature, it is best to add related tests.
   - Please follow [Contributor Covenant Code of 
Conduct](https://github.com/apache/brpc/blob/master/CODE_OF_CONDUCT.md).
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to