Hi experts, We notice that working directory change to '/' when enable nvme-cuse, and that cause some function error when using relative-path like open, fopen. The change working action call by fuse_daemonize() [patch: https://github.com/libfuse/libfuse/commit/c52c3256a5b0a586ab0c529ef765051...], This patch create in 2013. Is nvme-cuse feature consider this sence? Solved already? or Solve that by revert the fuse patch only? Any feedback was appreciated， we block by this issue for one week. Brs, Su Weifeng