diff --git a/cilium/cmd/cleanup.go b/cilium/cmd/cleanup.go
index <HASH>..<HASH> 100644
--- a/cilium/cmd/cleanup.go
+++ b/cilium/cmd/cleanup.go
@@ -76,7 +76,7 @@ func runCleanup() {
 	// errors seen, but continue.  So that one remove function does not
 	// prevent the remaining from running.
 	type cleanupFunc func() error
-	checks := []cleanupFunc{removeAllMaps, unmountFS, removeDirs, removeCNI}
+	checks := []cleanupFunc{removeAllMaps, removeDirs, removeCNI}
 	for _, clean := range checks {
 		if err := clean(); err != nil {
 			fmt.Fprintf(os.Stderr, "Error: %s\n", err)
@@ -145,13 +145,6 @@ func removeDirs() error {
 	return nil
 }
 
-func unmountFS() error {
-	if !bpf.IsBpffs(bpf.GetMapRoot()) {
-		return nil
-	}
-	return bpf.UnMountFS()
-}
-
 func removeAllMaps() error {
 	mapDir := bpf.MapPrefixPath()
 	maps, err := ioutil.ReadDir(mapDir)
cilium: Do not unmount BPF filesystem on cleanup

It does not seem wise to unmount the BPF filesystem on manual cleanup, it may
be in use by other components.