[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: uvm/busy page deadlock in current (related to loading Raspberry Pi 3B+ Wi-Fi firmware, but more of a timing bug with the VM system)
- To: Chuck Silvers <chuq%chuq.com@localhost>
- Subject: Re: uvm/busy page deadlock in current (related to loading Raspberry Pi 3B+ Wi-Fi firmware, but more of a timing bug with the VM system)
- From: Rob Newberry <robthedude%mac.com@localhost>
- Date: Wed, 19 Feb 2020 14:55:42 -0800
Thanks very much, Chuck -- glad to see things getting simplified!
> On Feb 18, 2020, at 12:39 PM, Chuck Silvers <chuq%chuq.com@localhost> wrote:
> eventually I realized that the aiodone_queue workqueue thread was
> made redundant long ago... we no longer need this mechanism to hand off
> any specific iodone processing to a worker thread because these days
> all iodone processing is done in a (softint) worker thread.
> I just commited a patch to remove this workqueue thread and associated code.
> On Wed, Feb 12, 2020 at 05:03:39PM -0800, Rob Newberry wrote:
>> Thanks very much, Chuck -- this patch fixed my problem.
>> I noticed you removed a couple of KASSERTs -- shouldn't those be cases be EVEN MORE true now than they were before? Given what I debugged, I'm wondering if the asserts would help make sure future code doesn't end up trying to do something similar in the future...
Main Index |
Thread Index |