On Tue, May 30, 2023 at 10:16:22AM -0700, Lucas De Marchi wrote: > On Tue, May 30, 2023 at 09:22:14AM -0700, Luis Chamberlain wrote: > > Lucas, any thoughts from modules kmod userspace perspective into > > supporting anyone likely issuing concurrent modules requests with > > differing arguments? > > Changing module params like that without first explicitly removing the > module was never supported by kmod or module-init-tools (I'm not digging > the history before 2.6 kernel) That's good enough. > During boot, note there is already a shortcut > if we have the sysfs node already in the "live" state or if the module is > built-in. In that case we will return success or -EEXIST (if the > KMOD_PROBE_IGNORE_LOADED flag was passed). Linus' code would make duplicates wait and share the same return value, ie, no new odd error code is returned. Or are you suggesting -EEXIST should be returned to duplicates if the module succeeded to load instead of 0 ? > The only scenario I can think of during boot in which the module params > could change would be when a buggy initrd is created, i.e. > /etc/modprobed.d/*.conf is in the rootfs but absent from initrd. This helps thanks. > So returning the same error code seems good to me. OK thanks! So just to confirm, it seems fine to return the same error code if duplicates wait, or do you prefer for some reason for there to be an exception and return -EEXIST if the module did succeed in the duplicate case? Luis
