Re: Is request_firmware() really safe to call in resume callback when /usr/lib/firmware is on btrfs?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello Luis,


On 18/08/2020 16:37, Luis Chamberlain wrote:
On Tue, Aug 18, 2020 at 12:04:51AM +0200, Lukas Middendorf wrote:
On 17/08/2020 17:20, Luis Chamberlain wrote:
This helps, thanks so much, now we'll have to write a reproducer, thanks
for the report!!

Will you do it yourself or do you expect me to do anything for this?

I meant to imply that we'd do this, now that we understand the problem. Thanks
for your report!

any news on this issue? Did you succeed with reproducing this at your end?

I retested this with 5.12-rc5 and everything still seems unchanged. I still get freezes on resume under the same circumstances described previously if /usr/lib/firmware is on btrfs. My patches to si2168.c were not merged. The documentation of request_firmware() seems unchanged and does not reflect the fact that prerequisites exist for making it safe to call during resume callbacks.

Lukas



[Index of Archives]     [Linux Input]     [Video for Linux]     [Gstreamer Embedded]     [Mplayer Users]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux