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

2021-04-02 Thread Luis Chamberlain
On Thu, Apr 01, 2021 at 04:59:47PM +0200, Lukas Middendorf wrote: > 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: > > &g

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

2021-04-02 Thread Luis Chamberlain
Lukas, can you share your /etc/fstab ? Also, how long do you stay in the boot before you try to suspend? Luis

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

2021-04-02 Thread Luis Chamberlain
On Fri, Apr 2, 2021 at 3:19 PM Luis Chamberlain wrote: > > Lukas, can you share your /etc/fstab ? Also, how long do you stay in > the boot before you try to suspend? OK I cannot reproduce the issue with the modified patch I sent to test_firmware, which if you enable config_enable_re

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

2021-04-03 Thread Luis Chamberlain
On Sat, Apr 03, 2021 at 12:24:07PM +0200, Lukas Middendorf wrote: > > On 02/04/2021 20:02, Luis Chamberlain wrote: > > No sorry, I dropped the ball on this but I managed to now spawn up the > > virtual guests where I was doing development to reproduce this. Give > > me s

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

2021-04-03 Thread Luis Chamberlain
On Sat, Apr 03, 2021 at 08:25:38PM +, Luis Chamberlain wrote: > So creating say 1000 random files in /lib/firmware on a freshly created > btrfs partition helps reproduce: > > mkfs.btrfs /dev/whatever > mount /dev/wahtever /lib/firmware > # Put it on /etc/fstab too > &

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

2021-04-08 Thread Luis Chamberlain
On Sat, Apr 03, 2021 at 08:25:38PM +, Luis Chamberlain wrote: > So creating say 1000 random files in /lib/firmware on a freshly created > btrfs partition helps reproduce: > > mkfs.btrfs /dev/whatever > mount /dev/wahtever /lib/firmware > # Put it on /etc/fstab too > &

Re: [RFC v3 0/2] vfs / btrfs: add support for ustat()

2021-04-15 Thread Luis Chamberlain
On Wed, Aug 23, 2017 at 3:31 PM Jeff Mahoney wrote: > > On 8/15/14 5:29 AM, Al Viro wrote: > > On Thu, Aug 14, 2014 at 07:58:56PM -0700, Luis R. Rodriguez wrote: > > > >> Christoph had noted that this seemed associated to the problem > >> that the btrfs uses different assignments for st_dev than s

Re: [RFC v3 0/2] vfs / btrfs: add support for ustat()

2021-04-15 Thread Luis Chamberlain
On Thu, Apr 15, 2021 at 02:17:58PM -0400, Josef Bacik wrote: > There's a lot of larger things that need to > be addressed in general to support the volume approach inside file systems > that is going to require a lot of work inside of VFS. If you feel like > tackling that work and then wiring up b

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

2021-04-16 Thread Luis Chamberlain
On Thu, Apr 08, 2021 at 06:02:24PM +, Luis Chamberlain wrote: > On Sat, Apr 03, 2021 at 08:25:38PM +0000, Luis Chamberlain wrote: > > So creating say 1000 random files in /lib/firmware on a freshly created > > btrfs partition helps reproduce: > > > > mkfs.btrfs /