Fengguang Wu <fengguang...@intel.com> writes: >> >> I tested by custom bdi with BDI_CAP_NO_WRITEBACK - sync(2) blocked >> >> forever by this reason. >> > >> > What's your test script? How do you create/use that custom bdi? >> >> Ah, I wrote my kernel module to test. I guess there is no users in >> current kernel for now, because it doesn't work. > > OK. Got it. So I'd suggest to change the first chunk to a VM_BUG_ON(), > which should be enough to catch new bad callers. The other two chunks > look fine.
Hm, if it changed to VM_BUG_ON(), we can't use BDI_CAP_NO_WRITEBACK to disable the writeback task (but allow inode cache reclaim) after all. Or you meant we don't allow to disable the writeback task? Thanks. -- OGAWA Hirofumi <hirof...@mail.parknet.co.jp> -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
