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?
Okay, so the warning is clearly being generated by the WARN_ON function in fs/super.c. dev_info" from either the files /include/ linux/backing- dev.h or /mm/backing-dev.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_
(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