On Thu, Aug 31, 2023 at 9:11 AM Christian Brauner <brauner@xxxxxxxxxx> wrote: > > > If that is good enough for people then I can grab it. > > > > Fine with me. And yes, I'd rather not have private data freed before > > SB_ACTIVE is cleared even if it is fine right now. It's just a bug > > waiting to happen. > > Applied to the vfs.super branch of the vfs/vfs.git tree. > Patches in the vfs.super branch should appear in linux-next soon. > > Please report any outstanding bugs that were missed during review in a > new review to the original patch series allowing us to drop it. > > It's encouraged to provide Acked-bys and Reviewed-bys even though the > patch has now been applied. If possible patch trailers will be updated. > > Note that commit hashes shown below are subject to change due to rebase, > trailer updates or similar. If in doubt, please check the listed branch. > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git > branch: vfs.super > > [1/4] ramfs: free sb->s_fs_info after shutting down the super block > https://git.kernel.org/vfs/vfs/c/c5725dff056d > [2/4] devpts: free sb->s_fs_info after shutting down the super block > https://git.kernel.org/vfs/vfs/c/fee7516be512 > [3/4] selinuxfs: free sb->s_fs_info after shutting down the super block > https://git.kernel.org/vfs/vfs/c/3105b94e7d62 > [4/4] hypfs: free sb->s_fs_info after shutting down the super block > https://git.kernel.org/vfs/vfs/c/993d214eb394 No need to change anything in this case, but in the future if there are no patch dependency or ordering issues can you let me take the SELinux patches via the SELinux tree? It helps prevent merge conflicts during the next merge window and quiets the daily automated checks I have in place to detect SELinux changes outside of the SELinux tree. Thanks. -- paul-moore.com
