From 518771e4e247762f60c5594de427a8c86f19bd57 Mon Sep 17 00:00:00 2001
From: Jakob Unterwurzacher
Date: Sun, 3 May 2020 15:22:10 +0200
Subject: fusefrontend_reverse: use inomap for inode number translation

Gets rid of static inode number value limitations.

Fixes https://github.com/rfjakob/gocryptfs/issues/457
---
 internal/fusefrontend_reverse/reverse_longnames.go | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'internal/fusefrontend_reverse/reverse_longnames.go')

diff --git a/internal/fusefrontend_reverse/reverse_longnames.go b/internal/fusefrontend_reverse/reverse_longnames.go
index f07e413..199356b 100644
--- a/internal/fusefrontend_reverse/reverse_longnames.go
+++ b/internal/fusefrontend_reverse/reverse_longnames.go
@@ -122,5 +122,5 @@ func (rfs *ReverseFS) newNameFile(relPath string) (nodefs.File, fuse.Status) {
 	}
 	content := []byte(rfs.nameTransform.EncryptName(pName, dirIV))
 	parentFile := filepath.Join(pDir, pName)
-	return rfs.newVirtualFile(content, rfs.args.Cipherdir, parentFile, inoBaseNameFile)
+	return rfs.newVirtualFile(content, rfs.args.Cipherdir, parentFile, inoTagNameFile)
 }
-- 
cgit v1.2.3