Quoting Justus Winter (2015-07-25 03:54:59) > I'm merely wondering whether we shouldn't protect > diskfs_reload_global_state with a lock. I'm not sure if concurrent > remounts are a problem, but they could very well be.
For the record, this is not a problem. There is the global diskfs_fsys_lock that prevents that. What happened to the corresponding fatfs change though? Isofs is read-only, and tmpfs' diskfs_reload_global_state is a nop too. So modulo the missing fatfs fix this patch looks good to me. Samuel, Thomas, is this still a smallish change that we can just merge, or do we need to do the paperwork now? Justus
