bgworker: handle disconnects on try_recv

[pykello]

No description provided.

[Copilot]

Pull Request Overview

This PR improves error handling in the background worker by properly detecting and handling channel disconnection scenarios. The change replaces a simple while loop with explicit error handling to gracefully shut down the worker when the request channel is disconnected.

• Replaces while loop with explicit match statement for better error handling
• Adds proper handling for channel disconnection with logging and worker shutdown
• Imports TryRecvError enum to enable error pattern matching

[greptile-apps]

Greptile Summary

This PR improves error handling in the background worker's message reception loop within the bdev_lazy module. The change replaces a while let Ok(req) = self.req_receiver.try_recv() pattern with an explicit match statement that handles all possible outcomes from try_recv().

The background worker (BgWorker) is a critical component in the lazy block device implementation that processes requests from other parts of the system via an MPSC (multi-producer, single-consumer) channel. Components like LazyIoChannel send BgWorkerRequest messages to this worker for processing.

The previous implementation only handled successful message reception and would silently ignore channel disconnection errors. This could result in the worker continuing to run indefinitely even after all message senders were dropped, leading to resource leaks and preventing proper system shutdown.

The new implementation explicitly handles three cases:

1. Ok(req) - Successfully received a request, processes it normally
2. Err(TryRecvError::Disconnected) - Channel is disconnected, logs an error, sets the worker's done flag, and returns early
3. Err(TryRecvError::Empty) - No messages available, breaks from the loop

This change ensures the background worker can detect when its communication channel is broken and shut itself down gracefully, which is essential in a system where components may be dynamically created and destroyed.

Confidence score: 5/5

• This PR is extremely safe to merge and significantly improves system reliability
• The change properly handles a critical edge case that could cause resource leaks and improper shutdown behavior
• No files need additional attention - the change is focused, well-implemented, and addresses a clear architectural concern

_{1 file reviewed, no comments}

_{Edit Code Review Bot Settings | Greptile}