Don't log warnings for incomplete Release requests in FUSE.

These are harmless errors, they generally happen as the test env is being
taken down. Linux does not check for the result of these requests either.
Logging a warning will cause tests to fail occasionally.

PiperOrigin-RevId: 821811305

Author: manninglucas

pkg/sentry/fsimpl/fuse/file.go

@@ -19,7 +19,6 @@ import (
 	"gvisor.dev/gvisor/pkg/atomicbitops"
 	"gvisor.dev/gvisor/pkg/context"
 	"gvisor.dev/gvisor/pkg/errors/linuxerr"
-	"gvisor.dev/gvisor/pkg/log"
 	"gvisor.dev/gvisor/pkg/sentry/fsimpl/kernfs"
 	"gvisor.dev/gvisor/pkg/sentry/kernel/auth"
 	"gvisor.dev/gvisor/pkg/sentry/vfs"
@@ -92,14 +91,7 @@ func (fd *fileDescription) Release(ctx context.Context) {
 	// Ignoring errors and FUSE server replies is analogous to Linux's behavior.
 	req := conn.NewRequest(auth.CredentialsFromContext(ctx), pidFromContext(ctx), inode.nodeID, opcode, &in)
 	// The reply will be ignored since no callback is defined in asyncCallBack().
-	res, err := conn.Call(ctx, req)
-	if err != nil {
-		log.Warningf("FUSE Release failed: %v", err)
-		return
-	}
-	if res.Error() != nil {
-		log.Warningf("FUSE Release failed: %v", res.Error())
-	}
+	conn.Call(ctx, req)
 }
 
 // OnClose implements vfs.FileDescriptionImpl.OnClose.