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
65954946
Commit
65954946
authored
Feb 27, 2015
by
Aaron Jacobs
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Renamed Lookup -> LookUpInode.
parent
b9b7ca4f
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
12 additions
and
11 deletions
+12
-11
file_system.go
file_system.go
+12
-11
No files found.
file_system.go
View file @
65954946
...
...
@@ -22,12 +22,12 @@ import (
type
FileSystem
interface
{
// Look up a child by name within a parent directory. The kernel calls this
// when resolving user paths to dentry structs, which are then cached.
Look
up
(
Look
UpInode
(
ctx
context
.
Context
,
req
*
Look
upRequest
)
(
*
Lookup
Response
,
error
)
req
*
Look
UpInodeRequest
)
(
*
LookUpInode
Response
,
error
)
// Forget an inode ID previously issued (e.g. by Look
up). The kernel calls
// this when removing an inode from its internal caches.
// Forget an inode ID previously issued (e.g. by Look
UpInode). The kernel
//
calls
this when removing an inode from its internal caches.
//
// The kernel guarantees that the node ID will not be used in further calls
// to the file system (unless it is reissued by the file system).
...
...
@@ -61,9 +61,10 @@ type FileSystem interface {
type
InodeID
uint64
// A distinguished inode ID that identifies the root of the file system, e.g.
// in a request to OpenDir or Lookup. Unlike all other inode IDs, which are
// minted by the file system, the FUSE VFS layer may send a request for this ID
// without the file system ever having referenced it in a previous response.
// in a request to OpenDir or LookUpInode. Unlike all other inode IDs, which
// are minted by the file system, the FUSE VFS layer may send a request for
// this ID without the file system ever having referenced it in a previous
// response.
const
RootInodeID
InodeID
=
InodeID
(
bazilfuse
.
RootID
)
// A generation number for an inode. Irrelevant for file systems that won't be
...
...
@@ -94,7 +95,7 @@ type InodeAttributes struct {
// Requests and responses
////////////////////////////////////////////////////////////////////////
type
Look
up
Request
struct
{
type
Look
UpInode
Request
struct
{
// The ID of the directory inode to which the child belongs.
Parent
InodeID
...
...
@@ -110,7 +111,7 @@ type LookupRequest struct {
Name
string
}
type
Look
up
Response
struct
{
type
Look
UpInode
Response
struct
{
// The ID of the child inode. The file system must ensure that the returned
// inode ID remains valid until a later call to ForgetInode.
Child
InodeID
...
...
@@ -164,8 +165,8 @@ type LookupResponse struct {
// FUSE file systems may spontaneously change their name -> inode mapping.
// Therefore the FUSE VFS layer uses dentry_operations::d_revalidate
// (http://goo.gl/dVea0h) to intercept lookups and revalidate by calling the
// user-space Look
up method. However the latter may be slow, so it caches the
// entries until the time defined by this field.
// user-space Look
UpInode method. However the latter may be slow, so it
//
caches the
entries until the time defined by this field.
//
// Example code walk:
//
...
...
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