Seems this was resolved in 4.12-rc2, mounting ntfs-3g volumes is fine,
doesn't generate a kernel warning! It was fixed in fs/fuse/inode.c at
https://github.com/torvalds/linux/commit/69c8ebf83213e6165b13d94ec599b861467ee2dc
with
diff --git a/fs/fuse/inode.c b/fs/fuse/inode.c
index 5a1b58f..65c8837
This was fixed in 4.12-rc2!
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
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
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_inf
** Attachment added: "dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692143/+attachment/4879845/+files/dmesg.log
--
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
** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692143/+attachment/4879867/+files/version.log
** Also affects: ntfs-3g (Ubuntu)
Importance: Undecided
Status: New
** Also affects: fuse (Ubuntu)
Importance: Undecided
Status: New
--
** Attachment added: "lspci-vvnn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692143/+attachment/4879846/+files/lspci-vvnn.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692143
T
** Attachment added: "uname-a.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692143/+attachment/4879847/+files/uname-a.log
--
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: