Hello, We've had a report[1] that depmod -a with a non-default umask (0027 in this case) can leave the produced modules.* files with permissions other than 0644. Now, this isn't really a bug because depmod is already explicit with its permissions and open/openat honor umask. It can, however, leave a machine in a state where non-root users can't read those files.
I'm curious if people think depmod should set its own explicit umask to ensure the file permissions are set to 0644. If so, I could create a patch to do this rather quickly. I wanted to get the upstream opinion on this situation first though. Thanks, josh [1] https://bugzilla.redhat.com/show_bug.cgi?id=893037 -- To unsubscribe from this list: send the line "unsubscribe linux-modules" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
