On Tue, 29 Oct 2019 13:47:38 -0700 Mike Kravetz <mike.kravetz@xxxxxxxxxx> wrote: > It is assumed that the hugetlbfs_vfsmount[] array will contain > either a valid vfsmount pointer or NULL for each hstate after > initialization. Changes made while converting to use fs_context > broke this assumption. > > While fixing the hugetlbfs_vfsmount issue, it was discovered that > init_hugetlbfs_fs never did correctly clean up when encountering > a vfs mount error. What were the user-visible runtime effects of this bug? (IOW: why does it warrant the cc:stable?)
