Commit | Line | Data |
---|---|---|
1da177e4 | 1 | |
5ea626aa | 2 | Overview of the Linux Virtual File System |
1da177e4 | 3 | |
5ea626aa | 4 | Original author: Richard Gooch <rgooch@atnf.csiro.au> |
1da177e4 | 5 | |
0746aec3 | 6 | Last updated on June 24, 2007. |
1da177e4 | 7 | |
5ea626aa PE |
8 | Copyright (C) 1999 Richard Gooch |
9 | Copyright (C) 2005 Pekka Enberg | |
1da177e4 | 10 | |
5ea626aa | 11 | This file is released under the GPLv2. |
1da177e4 | 12 | |
1da177e4 | 13 | |
cc7d1f8f PE |
14 | Introduction |
15 | ============ | |
1da177e4 | 16 | |
cc7d1f8f PE |
17 | The Virtual File System (also known as the Virtual Filesystem Switch) |
18 | is the software layer in the kernel that provides the filesystem | |
19 | interface to userspace programs. It also provides an abstraction | |
20 | within the kernel which allows different filesystem implementations to | |
21 | coexist. | |
1da177e4 | 22 | |
cc7d1f8f PE |
23 | VFS system calls open(2), stat(2), read(2), write(2), chmod(2) and so |
24 | on are called from a process context. Filesystem locking is described | |
25 | in the document Documentation/filesystems/Locking. | |
1da177e4 | 26 | |
1da177e4 | 27 | |
cc7d1f8f PE |
28 | Directory Entry Cache (dcache) |
29 | ------------------------------ | |
1da177e4 | 30 | |
cc7d1f8f PE |
31 | The VFS implements the open(2), stat(2), chmod(2), and similar system |
32 | calls. The pathname argument that is passed to them is used by the VFS | |
33 | to search through the directory entry cache (also known as the dentry | |
34 | cache or dcache). This provides a very fast look-up mechanism to | |
35 | translate a pathname (filename) into a specific dentry. Dentries live | |
36 | in RAM and are never saved to disc: they exist only for performance. | |
37 | ||
38 | The dentry cache is meant to be a view into your entire filespace. As | |
39 | most computers cannot fit all dentries in the RAM at the same time, | |
40 | some bits of the cache are missing. In order to resolve your pathname | |
41 | into a dentry, the VFS may have to resort to creating dentries along | |
42 | the way, and then loading the inode. This is done by looking up the | |
43 | inode. | |
44 | ||
45 | ||
46 | The Inode Object | |
47 | ---------------- | |
48 | ||
49 | An individual dentry usually has a pointer to an inode. Inodes are | |
50 | filesystem objects such as regular files, directories, FIFOs and other | |
51 | beasts. They live either on the disc (for block device filesystems) | |
52 | or in the memory (for pseudo filesystems). Inodes that live on the | |
53 | disc are copied into the memory when required and changes to the inode | |
54 | are written back to disc. A single inode can be pointed to by multiple | |
55 | dentries (hard links, for example, do this). | |
56 | ||
57 | To look up an inode requires that the VFS calls the lookup() method of | |
58 | the parent directory inode. This method is installed by the specific | |
59 | filesystem implementation that the inode lives in. Once the VFS has | |
60 | the required dentry (and hence the inode), we can do all those boring | |
61 | things like open(2) the file, or stat(2) it to peek at the inode | |
62 | data. The stat(2) operation is fairly simple: once the VFS has the | |
63 | dentry, it peeks at the inode data and passes some of it back to | |
64 | userspace. | |
65 | ||
66 | ||
67 | The File Object | |
68 | --------------- | |
1da177e4 LT |
69 | |
70 | Opening a file requires another operation: allocation of a file | |
71 | structure (this is the kernel-side implementation of file | |
5ea626aa | 72 | descriptors). The freshly allocated file structure is initialized with |
1da177e4 LT |
73 | a pointer to the dentry and a set of file operation member functions. |
74 | These are taken from the inode data. The open() file method is then | |
75 | called so the specific filesystem implementation can do it's work. You | |
cc7d1f8f PE |
76 | can see that this is another switch performed by the VFS. The file |
77 | structure is placed into the file descriptor table for the process. | |
1da177e4 LT |
78 | |
79 | Reading, writing and closing files (and other assorted VFS operations) | |
80 | is done by using the userspace file descriptor to grab the appropriate | |
cc7d1f8f PE |
81 | file structure, and then calling the required file structure method to |
82 | do whatever is required. For as long as the file is open, it keeps the | |
83 | dentry in use, which in turn means that the VFS inode is still in use. | |
1da177e4 | 84 | |
5ea626aa PE |
85 | |
86 | Registering and Mounting a Filesystem | |
cc7d1f8f | 87 | ===================================== |
1da177e4 | 88 | |
cc7d1f8f PE |
89 | To register and unregister a filesystem, use the following API |
90 | functions: | |
1da177e4 | 91 | |
cc7d1f8f | 92 | #include <linux/fs.h> |
1da177e4 | 93 | |
cc7d1f8f PE |
94 | extern int register_filesystem(struct file_system_type *); |
95 | extern int unregister_filesystem(struct file_system_type *); | |
1da177e4 | 96 | |
cc7d1f8f PE |
97 | The passed struct file_system_type describes your filesystem. When a |
98 | request is made to mount a device onto a directory in your filespace, | |
99 | the VFS will call the appropriate get_sb() method for the specific | |
100 | filesystem. The dentry for the mount point will then be updated to | |
101 | point to the root inode for the new filesystem. | |
1da177e4 | 102 | |
cc7d1f8f PE |
103 | You can see all filesystems that are registered to the kernel in the |
104 | file /proc/filesystems. | |
1da177e4 LT |
105 | |
106 | ||
5ea626aa | 107 | struct file_system_type |
cc7d1f8f | 108 | ----------------------- |
1da177e4 | 109 | |
0746aec3 | 110 | This describes the filesystem. As of kernel 2.6.22, the following |
1da177e4 LT |
111 | members are defined: |
112 | ||
113 | struct file_system_type { | |
114 | const char *name; | |
115 | int fs_flags; | |
5d8b2ebf JC |
116 | int (*get_sb) (struct file_system_type *, int, |
117 | const char *, void *, struct vfsmount *); | |
5ea626aa PE |
118 | void (*kill_sb) (struct super_block *); |
119 | struct module *owner; | |
120 | struct file_system_type * next; | |
121 | struct list_head fs_supers; | |
0746aec3 BP |
122 | struct lock_class_key s_lock_key; |
123 | struct lock_class_key s_umount_key; | |
1da177e4 LT |
124 | }; |
125 | ||
126 | name: the name of the filesystem type, such as "ext2", "iso9660", | |
127 | "msdos" and so on | |
128 | ||
129 | fs_flags: various flags (i.e. FS_REQUIRES_DEV, FS_NO_DCACHE, etc.) | |
130 | ||
5ea626aa | 131 | get_sb: the method to call when a new instance of this |
1da177e4 LT |
132 | filesystem should be mounted |
133 | ||
5ea626aa PE |
134 | kill_sb: the method to call when an instance of this filesystem |
135 | should be unmounted | |
136 | ||
137 | owner: for internal VFS use: you should initialize this to THIS_MODULE in | |
138 | most cases. | |
1da177e4 | 139 | |
5ea626aa PE |
140 | next: for internal VFS use: you should initialize this to NULL |
141 | ||
0746aec3 BP |
142 | s_lock_key, s_umount_key: lockdep-specific |
143 | ||
5ea626aa | 144 | The get_sb() method has the following arguments: |
1da177e4 | 145 | |
0746aec3 BP |
146 | struct file_system_type *fs_type: decribes the filesystem, partly initialized |
147 | by the specific filesystem code | |
5ea626aa PE |
148 | |
149 | int flags: mount flags | |
150 | ||
151 | const char *dev_name: the device name we are mounting. | |
1da177e4 LT |
152 | |
153 | void *data: arbitrary mount options, usually comes as an ASCII | |
154 | string | |
155 | ||
0746aec3 | 156 | struct vfsmount *mnt: a vfs-internal representation of a mount point |
1da177e4 | 157 | |
5ea626aa | 158 | The get_sb() method must determine if the block device specified |
0746aec3 BP |
159 | in the dev_name and fs_type contains a filesystem of the type the method |
160 | supports. If it succeeds in opening the named block device, it initializes a | |
161 | struct super_block descriptor for the filesystem contained by the block device. | |
162 | On failure it returns an error. | |
1da177e4 LT |
163 | |
164 | The most interesting member of the superblock structure that the | |
5ea626aa | 165 | get_sb() method fills in is the "s_op" field. This is a pointer to |
1da177e4 LT |
166 | a "struct super_operations" which describes the next level of the |
167 | filesystem implementation. | |
168 | ||
e3e1bfe4 JC |
169 | Usually, a filesystem uses one of the generic get_sb() implementations |
170 | and provides a fill_super() method instead. The generic methods are: | |
5ea626aa PE |
171 | |
172 | get_sb_bdev: mount a filesystem residing on a block device | |
1da177e4 | 173 | |
5ea626aa PE |
174 | get_sb_nodev: mount a filesystem that is not backed by a device |
175 | ||
176 | get_sb_single: mount a filesystem which shares the instance between | |
177 | all mounts | |
178 | ||
179 | A fill_super() method implementation has the following arguments: | |
180 | ||
181 | struct super_block *sb: the superblock structure. The method fill_super() | |
182 | must initialize this properly. | |
183 | ||
184 | void *data: arbitrary mount options, usually comes as an ASCII | |
185 | string | |
186 | ||
187 | int silent: whether or not to be silent on error | |
188 | ||
189 | ||
cc7d1f8f PE |
190 | The Superblock Object |
191 | ===================== | |
192 | ||
193 | A superblock object represents a mounted filesystem. | |
194 | ||
195 | ||
5ea626aa | 196 | struct super_operations |
cc7d1f8f | 197 | ----------------------- |
1da177e4 LT |
198 | |
199 | This describes how the VFS can manipulate the superblock of your | |
422b14c2 | 200 | filesystem. As of kernel 2.6.22, the following members are defined: |
1da177e4 LT |
201 | |
202 | struct super_operations { | |
5ea626aa PE |
203 | struct inode *(*alloc_inode)(struct super_block *sb); |
204 | void (*destroy_inode)(struct inode *); | |
205 | ||
206 | void (*read_inode) (struct inode *); | |
207 | ||
208 | void (*dirty_inode) (struct inode *); | |
209 | int (*write_inode) (struct inode *, int); | |
210 | void (*put_inode) (struct inode *); | |
211 | void (*drop_inode) (struct inode *); | |
212 | void (*delete_inode) (struct inode *); | |
213 | void (*put_super) (struct super_block *); | |
214 | void (*write_super) (struct super_block *); | |
215 | int (*sync_fs)(struct super_block *sb, int wait); | |
216 | void (*write_super_lockfs) (struct super_block *); | |
217 | void (*unlockfs) (struct super_block *); | |
726c3342 | 218 | int (*statfs) (struct dentry *, struct kstatfs *); |
5ea626aa PE |
219 | int (*remount_fs) (struct super_block *, int *, char *); |
220 | void (*clear_inode) (struct inode *); | |
221 | void (*umount_begin) (struct super_block *); | |
222 | ||
5ea626aa PE |
223 | int (*show_options)(struct seq_file *, struct vfsmount *); |
224 | ||
225 | ssize_t (*quota_read)(struct super_block *, int, char *, size_t, loff_t); | |
226 | ssize_t (*quota_write)(struct super_block *, int, const char *, size_t, loff_t); | |
1da177e4 LT |
227 | }; |
228 | ||
229 | All methods are called without any locks being held, unless otherwise | |
230 | noted. This means that most methods can block safely. All methods are | |
231 | only called from a process context (i.e. not from an interrupt handler | |
232 | or bottom half). | |
233 | ||
5ea626aa | 234 | alloc_inode: this method is called by inode_alloc() to allocate memory |
341546f5 N |
235 | for struct inode and initialize it. If this function is not |
236 | defined, a simple 'struct inode' is allocated. Normally | |
237 | alloc_inode will be used to allocate a larger structure which | |
238 | contains a 'struct inode' embedded within it. | |
5ea626aa PE |
239 | |
240 | destroy_inode: this method is called by destroy_inode() to release | |
341546f5 N |
241 | resources allocated for struct inode. It is only required if |
242 | ->alloc_inode was defined and simply undoes anything done by | |
243 | ->alloc_inode. | |
5ea626aa | 244 | |
1da177e4 | 245 | read_inode: this method is called to read a specific inode from the |
5ea626aa PE |
246 | mounted filesystem. The i_ino member in the struct inode is |
247 | initialized by the VFS to indicate which inode to read. Other | |
248 | members are filled in by this method. | |
249 | ||
250 | You can set this to NULL and use iget5_locked() instead of iget() | |
251 | to read inodes. This is necessary for filesystems for which the | |
252 | inode number is not sufficient to identify an inode. | |
253 | ||
254 | dirty_inode: this method is called by the VFS to mark an inode dirty. | |
1da177e4 LT |
255 | |
256 | write_inode: this method is called when the VFS needs to write an | |
257 | inode to disc. The second parameter indicates whether the write | |
258 | should be synchronous or not, not all filesystems check this flag. | |
259 | ||
260 | put_inode: called when the VFS inode is removed from the inode | |
5ea626aa | 261 | cache. |
1da177e4 LT |
262 | |
263 | drop_inode: called when the last access to the inode is dropped, | |
264 | with the inode_lock spinlock held. | |
265 | ||
5ea626aa | 266 | This method should be either NULL (normal UNIX filesystem |
1da177e4 LT |
267 | semantics) or "generic_delete_inode" (for filesystems that do not |
268 | want to cache inodes - causing "delete_inode" to always be | |
269 | called regardless of the value of i_nlink) | |
270 | ||
5ea626aa | 271 | The "generic_delete_inode()" behavior is equivalent to the |
1da177e4 LT |
272 | old practice of using "force_delete" in the put_inode() case, |
273 | but does not have the races that the "force_delete()" approach | |
274 | had. | |
275 | ||
276 | delete_inode: called when the VFS wants to delete an inode | |
277 | ||
1da177e4 LT |
278 | put_super: called when the VFS wishes to free the superblock |
279 | (i.e. unmount). This is called with the superblock lock held | |
280 | ||
281 | write_super: called when the VFS superblock needs to be written to | |
282 | disc. This method is optional | |
283 | ||
5ea626aa PE |
284 | sync_fs: called when VFS is writing out all dirty data associated with |
285 | a superblock. The second parameter indicates whether the method | |
286 | should wait until the write out has been completed. Optional. | |
287 | ||
cc7d1f8f PE |
288 | write_super_lockfs: called when VFS is locking a filesystem and |
289 | forcing it into a consistent state. This method is currently | |
290 | used by the Logical Volume Manager (LVM). | |
5ea626aa PE |
291 | |
292 | unlockfs: called when VFS is unlocking a filesystem and making it writable | |
293 | again. | |
294 | ||
1da177e4 LT |
295 | statfs: called when the VFS needs to get filesystem statistics. This |
296 | is called with the kernel lock held | |
297 | ||
298 | remount_fs: called when the filesystem is remounted. This is called | |
299 | with the kernel lock held | |
300 | ||
301 | clear_inode: called then the VFS clears the inode. Optional | |
302 | ||
5ea626aa PE |
303 | umount_begin: called when the VFS is unmounting a filesystem. |
304 | ||
5ea626aa PE |
305 | show_options: called by the VFS to show mount options for /proc/<pid>/mounts. |
306 | ||
307 | quota_read: called by the VFS to read from filesystem quota file. | |
308 | ||
309 | quota_write: called by the VFS to write to filesystem quota file. | |
310 | ||
1da177e4 LT |
311 | The read_inode() method is responsible for filling in the "i_op" |
312 | field. This is a pointer to a "struct inode_operations" which | |
313 | describes the methods that can be performed on individual inodes. | |
314 | ||
315 | ||
cc7d1f8f PE |
316 | The Inode Object |
317 | ================ | |
318 | ||
319 | An inode object represents an object within the filesystem. | |
320 | ||
321 | ||
5ea626aa | 322 | struct inode_operations |
cc7d1f8f | 323 | ----------------------- |
1da177e4 LT |
324 | |
325 | This describes how the VFS can manipulate an inode in your | |
422b14c2 | 326 | filesystem. As of kernel 2.6.22, the following members are defined: |
1da177e4 LT |
327 | |
328 | struct inode_operations { | |
5ea626aa PE |
329 | int (*create) (struct inode *,struct dentry *,int, struct nameidata *); |
330 | struct dentry * (*lookup) (struct inode *,struct dentry *, struct nameidata *); | |
1da177e4 LT |
331 | int (*link) (struct dentry *,struct inode *,struct dentry *); |
332 | int (*unlink) (struct inode *,struct dentry *); | |
333 | int (*symlink) (struct inode *,struct dentry *,const char *); | |
334 | int (*mkdir) (struct inode *,struct dentry *,int); | |
335 | int (*rmdir) (struct inode *,struct dentry *); | |
336 | int (*mknod) (struct inode *,struct dentry *,int,dev_t); | |
337 | int (*rename) (struct inode *, struct dentry *, | |
338 | struct inode *, struct dentry *); | |
5ea626aa PE |
339 | int (*readlink) (struct dentry *, char __user *,int); |
340 | void * (*follow_link) (struct dentry *, struct nameidata *); | |
341 | void (*put_link) (struct dentry *, struct nameidata *, void *); | |
1da177e4 | 342 | void (*truncate) (struct inode *); |
5ea626aa PE |
343 | int (*permission) (struct inode *, int, struct nameidata *); |
344 | int (*setattr) (struct dentry *, struct iattr *); | |
345 | int (*getattr) (struct vfsmount *mnt, struct dentry *, struct kstat *); | |
346 | int (*setxattr) (struct dentry *, const char *,const void *,size_t,int); | |
347 | ssize_t (*getxattr) (struct dentry *, const char *, void *, size_t); | |
348 | ssize_t (*listxattr) (struct dentry *, char *, size_t); | |
349 | int (*removexattr) (struct dentry *, const char *); | |
422b14c2 | 350 | void (*truncate_range)(struct inode *, loff_t, loff_t); |
1da177e4 LT |
351 | }; |
352 | ||
353 | Again, all methods are called without any locks being held, unless | |
354 | otherwise noted. | |
355 | ||
1da177e4 LT |
356 | create: called by the open(2) and creat(2) system calls. Only |
357 | required if you want to support regular files. The dentry you | |
358 | get should not have an inode (i.e. it should be a negative | |
359 | dentry). Here you will probably call d_instantiate() with the | |
360 | dentry and the newly created inode | |
361 | ||
362 | lookup: called when the VFS needs to look up an inode in a parent | |
363 | directory. The name to look for is found in the dentry. This | |
364 | method must call d_add() to insert the found inode into the | |
365 | dentry. The "i_count" field in the inode structure should be | |
366 | incremented. If the named inode does not exist a NULL inode | |
367 | should be inserted into the dentry (this is called a negative | |
368 | dentry). Returning an error code from this routine must only | |
369 | be done on a real error, otherwise creating inodes with system | |
370 | calls like create(2), mknod(2), mkdir(2) and so on will fail. | |
371 | If you wish to overload the dentry methods then you should | |
372 | initialise the "d_dop" field in the dentry; this is a pointer | |
373 | to a struct "dentry_operations". | |
374 | This method is called with the directory inode semaphore held | |
375 | ||
376 | link: called by the link(2) system call. Only required if you want | |
377 | to support hard links. You will probably need to call | |
378 | d_instantiate() just as you would in the create() method | |
379 | ||
380 | unlink: called by the unlink(2) system call. Only required if you | |
381 | want to support deleting inodes | |
382 | ||
383 | symlink: called by the symlink(2) system call. Only required if you | |
384 | want to support symlinks. You will probably need to call | |
385 | d_instantiate() just as you would in the create() method | |
386 | ||
387 | mkdir: called by the mkdir(2) system call. Only required if you want | |
388 | to support creating subdirectories. You will probably need to | |
389 | call d_instantiate() just as you would in the create() method | |
390 | ||
391 | rmdir: called by the rmdir(2) system call. Only required if you want | |
392 | to support deleting subdirectories | |
393 | ||
394 | mknod: called by the mknod(2) system call to create a device (char, | |
395 | block) inode or a named pipe (FIFO) or socket. Only required | |
396 | if you want to support creating these types of inodes. You | |
397 | will probably need to call d_instantiate() just as you would | |
398 | in the create() method | |
399 | ||
cc7d1f8f PE |
400 | rename: called by the rename(2) system call to rename the object to |
401 | have the parent and name given by the second inode and dentry. | |
402 | ||
1da177e4 LT |
403 | readlink: called by the readlink(2) system call. Only required if |
404 | you want to support reading symbolic links | |
405 | ||
406 | follow_link: called by the VFS to follow a symbolic link to the | |
5ea626aa | 407 | inode it points to. Only required if you want to support |
cc7d1f8f | 408 | symbolic links. This method returns a void pointer cookie |
5ea626aa PE |
409 | that is passed to put_link(). |
410 | ||
411 | put_link: called by the VFS to release resources allocated by | |
cc7d1f8f | 412 | follow_link(). The cookie returned by follow_link() is passed |
670e9f34 | 413 | to this method as the last parameter. It is used by |
cc7d1f8f PE |
414 | filesystems such as NFS where page cache is not stable |
415 | (i.e. page that was installed when the symbolic link walk | |
416 | started might not be in the page cache at the end of the | |
417 | walk). | |
418 | ||
419 | truncate: called by the VFS to change the size of a file. The | |
420 | i_size field of the inode is set to the desired size by the | |
421 | VFS before this method is called. This method is called by | |
422 | the truncate(2) system call and related functionality. | |
5ea626aa PE |
423 | |
424 | permission: called by the VFS to check for access rights on a POSIX-like | |
425 | filesystem. | |
426 | ||
cc7d1f8f PE |
427 | setattr: called by the VFS to set attributes for a file. This method |
428 | is called by chmod(2) and related system calls. | |
5ea626aa | 429 | |
cc7d1f8f PE |
430 | getattr: called by the VFS to get attributes of a file. This method |
431 | is called by stat(2) and related system calls. | |
5ea626aa PE |
432 | |
433 | setxattr: called by the VFS to set an extended attribute for a file. | |
cc7d1f8f PE |
434 | Extended attribute is a name:value pair associated with an |
435 | inode. This method is called by setxattr(2) system call. | |
436 | ||
437 | getxattr: called by the VFS to retrieve the value of an extended | |
438 | attribute name. This method is called by getxattr(2) function | |
439 | call. | |
440 | ||
441 | listxattr: called by the VFS to list all extended attributes for a | |
442 | given file. This method is called by listxattr(2) system call. | |
5ea626aa | 443 | |
cc7d1f8f PE |
444 | removexattr: called by the VFS to remove an extended attribute from |
445 | a file. This method is called by removexattr(2) system call. | |
5ea626aa | 446 | |
422b14c2 BP |
447 | truncate_range: a method provided by the underlying filesystem to truncate a |
448 | range of blocks , i.e. punch a hole somewhere in a file. | |
449 | ||
5ea626aa | 450 | |
cc7d1f8f PE |
451 | The Address Space Object |
452 | ======================== | |
453 | ||
341546f5 N |
454 | The address space object is used to group and manage pages in the page |
455 | cache. It can be used to keep track of the pages in a file (or | |
456 | anything else) and also track the mapping of sections of the file into | |
457 | process address spaces. | |
458 | ||
459 | There are a number of distinct yet related services that an | |
460 | address-space can provide. These include communicating memory | |
461 | pressure, page lookup by address, and keeping track of pages tagged as | |
462 | Dirty or Writeback. | |
463 | ||
a9e102b6 | 464 | The first can be used independently to the others. The VM can try to |
341546f5 N |
465 | either write dirty pages in order to clean them, or release clean |
466 | pages in order to reuse them. To do this it can call the ->writepage | |
467 | method on dirty pages, and ->releasepage on clean pages with | |
468 | PagePrivate set. Clean pages without PagePrivate and with no external | |
469 | references will be released without notice being given to the | |
470 | address_space. | |
471 | ||
a9e102b6 | 472 | To achieve this functionality, pages need to be placed on an LRU with |
341546f5 N |
473 | lru_cache_add and mark_page_active needs to be called whenever the |
474 | page is used. | |
475 | ||
476 | Pages are normally kept in a radix tree index by ->index. This tree | |
477 | maintains information about the PG_Dirty and PG_Writeback status of | |
478 | each page, so that pages with either of these flags can be found | |
479 | quickly. | |
480 | ||
481 | The Dirty tag is primarily used by mpage_writepages - the default | |
482 | ->writepages method. It uses the tag to find dirty pages to call | |
483 | ->writepage on. If mpage_writepages is not used (i.e. the address | |
a9e102b6 | 484 | provides its own ->writepages) , the PAGECACHE_TAG_DIRTY tag is |
341546f5 N |
485 | almost unused. write_inode_now and sync_inode do use it (through |
486 | __sync_single_inode) to check if ->writepages has been successful in | |
487 | writing out the whole address_space. | |
488 | ||
489 | The Writeback tag is used by filemap*wait* and sync_page* functions, | |
a9e102b6 | 490 | via wait_on_page_writeback_range, to wait for all writeback to |
341546f5 | 491 | complete. While waiting ->sync_page (if defined) will be called on |
a9e102b6 | 492 | each page that is found to require writeback. |
341546f5 N |
493 | |
494 | An address_space handler may attach extra information to a page, | |
495 | typically using the 'private' field in the 'struct page'. If such | |
496 | information is attached, the PG_Private flag should be set. This will | |
a9e102b6 | 497 | cause various VM routines to make extra calls into the address_space |
341546f5 N |
498 | handler to deal with that data. |
499 | ||
500 | An address space acts as an intermediate between storage and | |
501 | application. Data is read into the address space a whole page at a | |
502 | time, and provided to the application either by copying of the page, | |
503 | or by memory-mapping the page. | |
504 | Data is written into the address space by the application, and then | |
505 | written-back to storage typically in whole pages, however the | |
a9e102b6 | 506 | address_space has finer control of write sizes. |
341546f5 N |
507 | |
508 | The read process essentially only requires 'readpage'. The write | |
509 | process is more complicated and uses prepare_write/commit_write or | |
510 | set_page_dirty to write data into the address_space, and writepage, | |
511 | sync_page, and writepages to writeback data to storage. | |
512 | ||
513 | Adding and removing pages to/from an address_space is protected by the | |
514 | inode's i_mutex. | |
515 | ||
516 | When data is written to a page, the PG_Dirty flag should be set. It | |
517 | typically remains set until writepage asks for it to be written. This | |
518 | should clear PG_Dirty and set PG_Writeback. It can be actually | |
519 | written at any point after PG_Dirty is clear. Once it is known to be | |
520 | safe, PG_Writeback is cleared. | |
521 | ||
522 | Writeback makes use of a writeback_control structure... | |
5ea626aa PE |
523 | |
524 | struct address_space_operations | |
cc7d1f8f | 525 | ------------------------------- |
5ea626aa PE |
526 | |
527 | This describes how the VFS can manipulate mapping of a file to page cache in | |
422b14c2 | 528 | your filesystem. As of kernel 2.6.22, the following members are defined: |
5ea626aa PE |
529 | |
530 | struct address_space_operations { | |
531 | int (*writepage)(struct page *page, struct writeback_control *wbc); | |
532 | int (*readpage)(struct file *, struct page *); | |
533 | int (*sync_page)(struct page *); | |
534 | int (*writepages)(struct address_space *, struct writeback_control *); | |
535 | int (*set_page_dirty)(struct page *page); | |
536 | int (*readpages)(struct file *filp, struct address_space *mapping, | |
537 | struct list_head *pages, unsigned nr_pages); | |
538 | int (*prepare_write)(struct file *, struct page *, unsigned, unsigned); | |
539 | int (*commit_write)(struct file *, struct page *, unsigned, unsigned); | |
540 | sector_t (*bmap)(struct address_space *, sector_t); | |
541 | int (*invalidatepage) (struct page *, unsigned long); | |
542 | int (*releasepage) (struct page *, int); | |
543 | ssize_t (*direct_IO)(int, struct kiocb *, const struct iovec *iov, | |
544 | loff_t offset, unsigned long nr_segs); | |
545 | struct page* (*get_xip_page)(struct address_space *, sector_t, | |
546 | int); | |
341546f5 N |
547 | /* migrate the contents of a page to the specified target */ |
548 | int (*migratepage) (struct page *, struct page *); | |
422b14c2 | 549 | int (*launder_page) (struct page *); |
5ea626aa PE |
550 | }; |
551 | ||
341546f5 | 552 | writepage: called by the VM to write a dirty page to backing store. |
a9e102b6 | 553 | This may happen for data integrity reasons (i.e. 'sync'), or |
341546f5 N |
554 | to free up memory (flush). The difference can be seen in |
555 | wbc->sync_mode. | |
556 | The PG_Dirty flag has been cleared and PageLocked is true. | |
557 | writepage should start writeout, should set PG_Writeback, | |
558 | and should make sure the page is unlocked, either synchronously | |
559 | or asynchronously when the write operation completes. | |
560 | ||
561 | If wbc->sync_mode is WB_SYNC_NONE, ->writepage doesn't have to | |
a9e102b6 N |
562 | try too hard if there are problems, and may choose to write out |
563 | other pages from the mapping if that is easier (e.g. due to | |
564 | internal dependencies). If it chooses not to start writeout, it | |
565 | should return AOP_WRITEPAGE_ACTIVATE so that the VM will not keep | |
341546f5 N |
566 | calling ->writepage on that page. |
567 | ||
568 | See the file "Locking" for more details. | |
5ea626aa PE |
569 | |
570 | readpage: called by the VM to read a page from backing store. | |
341546f5 N |
571 | The page will be Locked when readpage is called, and should be |
572 | unlocked and marked uptodate once the read completes. | |
573 | If ->readpage discovers that it needs to unlock the page for | |
574 | some reason, it can do so, and then return AOP_TRUNCATED_PAGE. | |
a9e102b6 | 575 | In this case, the page will be relocated, relocked and if |
341546f5 | 576 | that all succeeds, ->readpage will be called again. |
5ea626aa PE |
577 | |
578 | sync_page: called by the VM to notify the backing store to perform all | |
579 | queued I/O operations for a page. I/O operations for other pages | |
580 | associated with this address_space object may also be performed. | |
581 | ||
341546f5 N |
582 | This function is optional and is called only for pages with |
583 | PG_Writeback set while waiting for the writeback to complete. | |
584 | ||
5ea626aa | 585 | writepages: called by the VM to write out pages associated with the |
a9e102b6 N |
586 | address_space object. If wbc->sync_mode is WBC_SYNC_ALL, then |
587 | the writeback_control will specify a range of pages that must be | |
588 | written out. If it is WBC_SYNC_NONE, then a nr_to_write is given | |
341546f5 N |
589 | and that many pages should be written if possible. |
590 | If no ->writepages is given, then mpage_writepages is used | |
a9e102b6 | 591 | instead. This will choose pages from the address space that are |
341546f5 | 592 | tagged as DIRTY and will pass them to ->writepage. |
5ea626aa PE |
593 | |
594 | set_page_dirty: called by the VM to set a page dirty. | |
341546f5 N |
595 | This is particularly needed if an address space attaches |
596 | private data to a page, and that data needs to be updated when | |
597 | a page is dirtied. This is called, for example, when a memory | |
598 | mapped page gets modified. | |
599 | If defined, it should set the PageDirty flag, and the | |
600 | PAGECACHE_TAG_DIRTY tag in the radix tree. | |
5ea626aa PE |
601 | |
602 | readpages: called by the VM to read pages associated with the address_space | |
341546f5 N |
603 | object. This is essentially just a vector version of |
604 | readpage. Instead of just one page, several pages are | |
605 | requested. | |
a9e102b6 | 606 | readpages is only used for read-ahead, so read errors are |
341546f5 | 607 | ignored. If anything goes wrong, feel free to give up. |
1da177e4 | 608 | |
5ea626aa | 609 | prepare_write: called by the generic write path in VM to set up a write |
341546f5 | 610 | request for a page. This indicates to the address space that |
a9e102b6 | 611 | the given range of bytes is about to be written. The |
341546f5 N |
612 | address_space should check that the write will be able to |
613 | complete, by allocating space if necessary and doing any other | |
a9e102b6 | 614 | internal housekeeping. If the write will update parts of |
341546f5 N |
615 | any basic-blocks on storage, then those blocks should be |
616 | pre-read (if they haven't been read already) so that the | |
617 | updated blocks can be written out properly. | |
618 | The page will be locked. If prepare_write wants to unlock the | |
619 | page it, like readpage, may do so and return | |
620 | AOP_TRUNCATED_PAGE. | |
621 | In this case the prepare_write will be retried one the lock is | |
622 | regained. | |
623 | ||
955eff5a NP |
624 | Note: the page _must not_ be marked uptodate in this function |
625 | (or anywhere else) unless it actually is uptodate right now. As | |
626 | soon as a page is marked uptodate, it is possible for a concurrent | |
627 | read(2) to copy it to userspace. | |
628 | ||
341546f5 N |
629 | commit_write: If prepare_write succeeds, new data will be copied |
630 | into the page and then commit_write will be called. It will | |
631 | typically update the size of the file (if appropriate) and | |
632 | mark the inode as dirty, and do any other related housekeeping | |
633 | operations. It should avoid returning an error if possible - | |
634 | errors should have been handled by prepare_write. | |
5ea626aa PE |
635 | |
636 | bmap: called by the VFS to map a logical block offset within object to | |
a9e102b6 | 637 | physical block number. This method is used by the FIBMAP |
341546f5 | 638 | ioctl and for working with swap-files. To be able to swap to |
a9e102b6 | 639 | a file, the file must have a stable mapping to a block |
341546f5 N |
640 | device. The swap system does not go through the filesystem |
641 | but instead uses bmap to find out where the blocks in the file | |
642 | are and uses those addresses directly. | |
643 | ||
644 | ||
645 | invalidatepage: If a page has PagePrivate set, then invalidatepage | |
646 | will be called when part or all of the page is to be removed | |
a9e102b6 | 647 | from the address space. This generally corresponds to either a |
341546f5 N |
648 | truncation or a complete invalidation of the address space |
649 | (in the latter case 'offset' will always be 0). | |
650 | Any private data associated with the page should be updated | |
651 | to reflect this truncation. If offset is 0, then | |
652 | the private data should be released, because the page | |
653 | must be able to be completely discarded. This may be done by | |
654 | calling the ->releasepage function, but in this case the | |
655 | release MUST succeed. | |
656 | ||
657 | releasepage: releasepage is called on PagePrivate pages to indicate | |
658 | that the page should be freed if possible. ->releasepage | |
659 | should remove any private data from the page and clear the | |
660 | PagePrivate flag. It may also remove the page from the | |
661 | address_space. If this fails for some reason, it may indicate | |
662 | failure with a 0 return value. | |
663 | This is used in two distinct though related cases. The first | |
664 | is when the VM finds a clean page with no active users and | |
665 | wants to make it a free page. If ->releasepage succeeds, the | |
666 | page will be removed from the address_space and become free. | |
667 | ||
668 | The second case if when a request has been made to invalidate | |
669 | some or all pages in an address_space. This can happen | |
670 | through the fadvice(POSIX_FADV_DONTNEED) system call or by the | |
671 | filesystem explicitly requesting it as nfs and 9fs do (when | |
672 | they believe the cache may be out of date with storage) by | |
673 | calling invalidate_inode_pages2(). | |
674 | If the filesystem makes such a call, and needs to be certain | |
a9e102b6 | 675 | that all pages are invalidated, then its releasepage will |
341546f5 N |
676 | need to ensure this. Possibly it can clear the PageUptodate |
677 | bit if it cannot free private data yet. | |
678 | ||
679 | direct_IO: called by the generic read/write routines to perform | |
680 | direct_IO - that is IO requests which bypass the page cache | |
a9e102b6 | 681 | and transfer data directly between the storage and the |
341546f5 | 682 | application's address space. |
5ea626aa PE |
683 | |
684 | get_xip_page: called by the VM to translate a block number to a page. | |
685 | The page is valid until the corresponding filesystem is unmounted. | |
686 | Filesystems that want to use execute-in-place (XIP) need to implement | |
687 | it. An example implementation can be found in fs/ext2/xip.c. | |
688 | ||
341546f5 N |
689 | migrate_page: This is used to compact the physical memory usage. |
690 | If the VM wants to relocate a page (maybe off a memory card | |
691 | that is signalling imminent failure) it will pass a new page | |
692 | and an old page to this function. migrate_page should | |
693 | transfer any private data across and update any references | |
694 | that it has to the page. | |
5ea626aa | 695 | |
422b14c2 BP |
696 | launder_page: Called before freeing a page - it writes back the dirty page. To |
697 | prevent redirtying the page, it is kept locked during the whole | |
698 | operation. | |
699 | ||
cc7d1f8f PE |
700 | The File Object |
701 | =============== | |
702 | ||
703 | A file object represents a file opened by a process. | |
704 | ||
705 | ||
5ea626aa | 706 | struct file_operations |
cc7d1f8f | 707 | ---------------------- |
1da177e4 LT |
708 | |
709 | This describes how the VFS can manipulate an open file. As of kernel | |
422b14c2 | 710 | 2.6.22, the following members are defined: |
1da177e4 LT |
711 | |
712 | struct file_operations { | |
422b14c2 | 713 | struct module *owner; |
1da177e4 | 714 | loff_t (*llseek) (struct file *, loff_t, int); |
5ea626aa | 715 | ssize_t (*read) (struct file *, char __user *, size_t, loff_t *); |
5ea626aa | 716 | ssize_t (*write) (struct file *, const char __user *, size_t, loff_t *); |
027445c3 BP |
717 | ssize_t (*aio_read) (struct kiocb *, const struct iovec *, unsigned long, loff_t); |
718 | ssize_t (*aio_write) (struct kiocb *, const struct iovec *, unsigned long, loff_t); | |
1da177e4 LT |
719 | int (*readdir) (struct file *, void *, filldir_t); |
720 | unsigned int (*poll) (struct file *, struct poll_table_struct *); | |
721 | int (*ioctl) (struct inode *, struct file *, unsigned int, unsigned long); | |
5ea626aa PE |
722 | long (*unlocked_ioctl) (struct file *, unsigned int, unsigned long); |
723 | long (*compat_ioctl) (struct file *, unsigned int, unsigned long); | |
1da177e4 LT |
724 | int (*mmap) (struct file *, struct vm_area_struct *); |
725 | int (*open) (struct inode *, struct file *); | |
5ea626aa | 726 | int (*flush) (struct file *); |
1da177e4 | 727 | int (*release) (struct inode *, struct file *); |
5ea626aa PE |
728 | int (*fsync) (struct file *, struct dentry *, int datasync); |
729 | int (*aio_fsync) (struct kiocb *, int datasync); | |
730 | int (*fasync) (int, struct file *, int); | |
1da177e4 | 731 | int (*lock) (struct file *, int, struct file_lock *); |
5ea626aa PE |
732 | ssize_t (*readv) (struct file *, const struct iovec *, unsigned long, loff_t *); |
733 | ssize_t (*writev) (struct file *, const struct iovec *, unsigned long, loff_t *); | |
734 | ssize_t (*sendfile) (struct file *, loff_t *, size_t, read_actor_t, void *); | |
735 | ssize_t (*sendpage) (struct file *, struct page *, int, size_t, loff_t *, int); | |
736 | unsigned long (*get_unmapped_area)(struct file *, unsigned long, unsigned long, unsigned long, unsigned long); | |
737 | int (*check_flags)(int); | |
738 | int (*dir_notify)(struct file *filp, unsigned long arg); | |
739 | int (*flock) (struct file *, int, struct file_lock *); | |
422b14c2 BP |
740 | ssize_t (*splice_write)(struct pipe_inode_info *, struct file *, size_t, unsigned int); |
741 | ssize_t (*splice_read)(struct file *, struct pipe_inode_info *, size_t, unsigned int); | |
1da177e4 LT |
742 | }; |
743 | ||
744 | Again, all methods are called without any locks being held, unless | |
745 | otherwise noted. | |
746 | ||
747 | llseek: called when the VFS needs to move the file position index | |
748 | ||
749 | read: called by read(2) and related system calls | |
750 | ||
5ea626aa PE |
751 | aio_read: called by io_submit(2) and other asynchronous I/O operations |
752 | ||
1da177e4 LT |
753 | write: called by write(2) and related system calls |
754 | ||
5ea626aa PE |
755 | aio_write: called by io_submit(2) and other asynchronous I/O operations |
756 | ||
1da177e4 LT |
757 | readdir: called when the VFS needs to read the directory contents |
758 | ||
759 | poll: called by the VFS when a process wants to check if there is | |
760 | activity on this file and (optionally) go to sleep until there | |
761 | is activity. Called by the select(2) and poll(2) system calls | |
762 | ||
763 | ioctl: called by the ioctl(2) system call | |
764 | ||
5ea626aa PE |
765 | unlocked_ioctl: called by the ioctl(2) system call. Filesystems that do not |
766 | require the BKL should use this method instead of the ioctl() above. | |
767 | ||
768 | compat_ioctl: called by the ioctl(2) system call when 32 bit system calls | |
769 | are used on 64 bit kernels. | |
770 | ||
1da177e4 LT |
771 | mmap: called by the mmap(2) system call |
772 | ||
773 | open: called by the VFS when an inode should be opened. When the VFS | |
5ea626aa PE |
774 | opens a file, it creates a new "struct file". It then calls the |
775 | open method for the newly allocated file structure. You might | |
776 | think that the open method really belongs in | |
777 | "struct inode_operations", and you may be right. I think it's | |
778 | done the way it is because it makes filesystems simpler to | |
779 | implement. The open() method is a good place to initialize the | |
780 | "private_data" member in the file structure if you want to point | |
781 | to a device structure | |
782 | ||
783 | flush: called by the close(2) system call to flush a file | |
1da177e4 LT |
784 | |
785 | release: called when the last reference to an open file is closed | |
786 | ||
787 | fsync: called by the fsync(2) system call | |
788 | ||
789 | fasync: called by the fcntl(2) system call when asynchronous | |
790 | (non-blocking) mode is enabled for a file | |
791 | ||
5ea626aa PE |
792 | lock: called by the fcntl(2) system call for F_GETLK, F_SETLK, and F_SETLKW |
793 | commands | |
794 | ||
795 | readv: called by the readv(2) system call | |
796 | ||
797 | writev: called by the writev(2) system call | |
798 | ||
799 | sendfile: called by the sendfile(2) system call | |
800 | ||
801 | get_unmapped_area: called by the mmap(2) system call | |
802 | ||
803 | check_flags: called by the fcntl(2) system call for F_SETFL command | |
804 | ||
805 | dir_notify: called by the fcntl(2) system call for F_NOTIFY command | |
806 | ||
807 | flock: called by the flock(2) system call | |
808 | ||
d1195c51 PE |
809 | splice_write: called by the VFS to splice data from a pipe to a file. This |
810 | method is used by the splice(2) system call | |
811 | ||
812 | splice_read: called by the VFS to splice data from file to a pipe. This | |
813 | method is used by the splice(2) system call | |
814 | ||
1da177e4 LT |
815 | Note that the file operations are implemented by the specific |
816 | filesystem in which the inode resides. When opening a device node | |
817 | (character or block special) most filesystems will call special | |
818 | support routines in the VFS which will locate the required device | |
819 | driver information. These support routines replace the filesystem file | |
820 | operations with those for the device driver, and then proceed to call | |
821 | the new open() method for the file. This is how opening a device file | |
822 | in the filesystem eventually ends up calling the device driver open() | |
5ea626aa | 823 | method. |
1da177e4 LT |
824 | |
825 | ||
5ea626aa PE |
826 | Directory Entry Cache (dcache) |
827 | ============================== | |
828 | ||
1da177e4 LT |
829 | |
830 | struct dentry_operations | |
5ea626aa | 831 | ------------------------ |
1da177e4 LT |
832 | |
833 | This describes how a filesystem can overload the standard dentry | |
834 | operations. Dentries and the dcache are the domain of the VFS and the | |
835 | individual filesystem implementations. Device drivers have no business | |
836 | here. These methods may be set to NULL, as they are either optional or | |
c23fbb6b | 837 | the VFS uses a default. As of kernel 2.6.22, the following members are |
1da177e4 LT |
838 | defined: |
839 | ||
840 | struct dentry_operations { | |
5ea626aa | 841 | int (*d_revalidate)(struct dentry *, struct nameidata *); |
1da177e4 LT |
842 | int (*d_hash) (struct dentry *, struct qstr *); |
843 | int (*d_compare) (struct dentry *, struct qstr *, struct qstr *); | |
5ea626aa | 844 | int (*d_delete)(struct dentry *); |
1da177e4 LT |
845 | void (*d_release)(struct dentry *); |
846 | void (*d_iput)(struct dentry *, struct inode *); | |
c23fbb6b | 847 | char *(*d_dname)(struct dentry *, char *, int); |
1da177e4 LT |
848 | }; |
849 | ||
850 | d_revalidate: called when the VFS needs to revalidate a dentry. This | |
851 | is called whenever a name look-up finds a dentry in the | |
852 | dcache. Most filesystems leave this as NULL, because all their | |
853 | dentries in the dcache are valid | |
854 | ||
855 | d_hash: called when the VFS adds a dentry to the hash table | |
856 | ||
857 | d_compare: called when a dentry should be compared with another | |
858 | ||
859 | d_delete: called when the last reference to a dentry is | |
860 | deleted. This means no-one is using the dentry, however it is | |
861 | still valid and in the dcache | |
862 | ||
863 | d_release: called when a dentry is really deallocated | |
864 | ||
865 | d_iput: called when a dentry loses its inode (just prior to its | |
866 | being deallocated). The default when this is NULL is that the | |
867 | VFS calls iput(). If you define this method, you must call | |
868 | iput() yourself | |
869 | ||
c23fbb6b ED |
870 | d_dname: called when the pathname of a dentry should be generated. |
871 | Usefull for some pseudo filesystems (sockfs, pipefs, ...) to delay | |
872 | pathname generation. (Instead of doing it when dentry is created, | |
873 | its done only when the path is needed.). Real filesystems probably | |
874 | dont want to use it, because their dentries are present in global | |
875 | dcache hash, so their hash should be an invariant. As no lock is | |
876 | held, d_dname() should not try to modify the dentry itself, unless | |
877 | appropriate SMP safety is used. CAUTION : d_path() logic is quite | |
878 | tricky. The correct way to return for example "Hello" is to put it | |
879 | at the end of the buffer, and returns a pointer to the first char. | |
880 | dynamic_dname() helper function is provided to take care of this. | |
881 | ||
882 | Example : | |
883 | ||
884 | static char *pipefs_dname(struct dentry *dent, char *buffer, int buflen) | |
885 | { | |
886 | return dynamic_dname(dentry, buffer, buflen, "pipe:[%lu]", | |
887 | dentry->d_inode->i_ino); | |
888 | } | |
889 | ||
1da177e4 LT |
890 | Each dentry has a pointer to its parent dentry, as well as a hash list |
891 | of child dentries. Child dentries are basically like files in a | |
892 | directory. | |
893 | ||
5ea626aa | 894 | |
cc7d1f8f | 895 | Directory Entry Cache API |
1da177e4 LT |
896 | -------------------------- |
897 | ||
898 | There are a number of functions defined which permit a filesystem to | |
899 | manipulate dentries: | |
900 | ||
901 | dget: open a new handle for an existing dentry (this just increments | |
902 | the usage count) | |
903 | ||
904 | dput: close a handle for a dentry (decrements the usage count). If | |
905 | the usage count drops to 0, the "d_delete" method is called | |
906 | and the dentry is placed on the unused list if the dentry is | |
907 | still in its parents hash list. Putting the dentry on the | |
908 | unused list just means that if the system needs some RAM, it | |
909 | goes through the unused list of dentries and deallocates them. | |
910 | If the dentry has already been unhashed and the usage count | |
911 | drops to 0, in this case the dentry is deallocated after the | |
912 | "d_delete" method is called | |
913 | ||
914 | d_drop: this unhashes a dentry from its parents hash list. A | |
5ea626aa | 915 | subsequent call to dput() will deallocate the dentry if its |
1da177e4 LT |
916 | usage count drops to 0 |
917 | ||
918 | d_delete: delete a dentry. If there are no other open references to | |
919 | the dentry then the dentry is turned into a negative dentry | |
920 | (the d_iput() method is called). If there are other | |
921 | references, then d_drop() is called instead | |
922 | ||
923 | d_add: add a dentry to its parents hash list and then calls | |
924 | d_instantiate() | |
925 | ||
926 | d_instantiate: add a dentry to the alias hash list for the inode and | |
927 | updates the "d_inode" member. The "i_count" member in the | |
928 | inode structure should be set/incremented. If the inode | |
929 | pointer is NULL, the dentry is called a "negative | |
930 | dentry". This function is commonly called when an inode is | |
931 | created for an existing negative dentry | |
932 | ||
933 | d_lookup: look up a dentry given its parent and path name component | |
934 | It looks up the child of that given name from the dcache | |
935 | hash table. If it is found, the reference count is incremented | |
936 | and the dentry is returned. The caller must use d_put() | |
937 | to free the dentry when it finishes using it. | |
938 | ||
cbf8f0f3 PE |
939 | For further information on dentry locking, please refer to the document |
940 | Documentation/filesystems/dentry-locking.txt. | |
cc7d1f8f PE |
941 | |
942 | ||
943 | Resources | |
944 | ========= | |
945 | ||
946 | (Note some of these resources are not up-to-date with the latest kernel | |
947 | version.) | |
948 | ||
949 | Creating Linux virtual filesystems. 2002 | |
950 | <http://lwn.net/Articles/13325/> | |
951 | ||
952 | The Linux Virtual File-system Layer by Neil Brown. 1999 | |
953 | <http://www.cse.unsw.edu.au/~neilb/oss/linux-commentary/vfs.html> | |
954 | ||
955 | A tour of the Linux VFS by Michael K. Johnson. 1996 | |
956 | <http://www.tldp.org/LDP/khg/HyperNews/get/fs/vfstour.html> | |
957 | ||
958 | A small trail through the Linux kernel by Andries Brouwer. 2001 | |
959 | <http://www.win.tue.nl/~aeb/linux/vfs/trail.html> |