Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
J
jacobsa-fuse
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
jacobsa-fuse
Commits
3cb67f58
Commit
3cb67f58
authored
Jun 09, 2015
by
Aaron Jacobs
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Tightened forgetfs's post-destruction check, now that we can.
parent
43c8f9d8
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
0 additions
and
13 deletions
+0
-13
samples/forgetfs/forget_fs.go
samples/forgetfs/forget_fs.go
+0
-13
No files found.
samples/forgetfs/forget_fs.go
View file @
3cb67f58
...
@@ -196,19 +196,6 @@ func (fs *fsImpl) Check() {
...
@@ -196,19 +196,6 @@ func (fs *fsImpl) Check() {
defer
fs
.
mu
.
Unlock
()
defer
fs
.
mu
.
Unlock
()
for
k
,
v
:=
range
fs
.
inodes
{
for
k
,
v
:=
range
fs
.
inodes
{
// Special case: we don't require the root inode to have reached zero.
// OS X doesn't seem to send forgets for the root, and Linux only does
// sometimes. But we want to make sure it's not greater than one, which
// would be weird.
if
k
==
fuseops
.
RootInodeID
{
if
v
.
lookupCount
>
1
{
panic
(
fmt
.
Sprintf
(
"Root has lookup count %v"
,
v
.
lookupCount
))
}
continue
}
// Check other inodes.
if
v
.
lookupCount
!=
0
{
if
v
.
lookupCount
!=
0
{
panic
(
fmt
.
Sprintf
(
"Inode %v has lookup count %v"
,
k
,
v
.
lookupCount
))
panic
(
fmt
.
Sprintf
(
"Inode %v has lookup count %v"
,
k
,
v
.
lookupCount
))
}
}
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment