Okay, so the warning is clearly being generated by the WARN_ON function in fs/super.c. I realize I could disable the warning, but that sounds like a bad idea. One question though, why would we be verifying if sb->s_bdi is equal to the address of some "struct backing_dev_info noop_backing_dev_info" from either the files /include/linux/backing-dev.h or /mm/backing-dev.c (Found references to definition of this struct in these two file using the power of grep -rl) in fs/super.c on line 1281, when we reassign it anyway to a local variable bdi right after? In other words, IS there something going wrong here, or is this warning insignificant and should be removed?
1281: WARN_ON(sb->s_bdi != &noop_backing_dev_info); 1282: sb->s_bdi = bdi; Also see bug report I filed about this problem at https://bugzilla.kernel.org/show_bug.cgi?id=195809 ** Bug watch added: Linux Kernel Bug Tracker #195809 https://bugzilla.kernel.org/show_bug.cgi?id=195809 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1692143 Title: fs changes in kernel 4.12 break mount of ntfs-3g, possible data corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fuse/+bug/1692143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
