diff options
| author | Frans Kaashoek <kaashoek@mit.edu> | 2019-08-17 12:52:25 -0400 |
|---|---|---|
| committer | Frans Kaashoek <kaashoek@mit.edu> | 2019-08-17 12:52:25 -0400 |
| commit | a9953236cc9f1befb625575671bc39f1ab254bf0 (patch) | |
| tree | debd66f05ec6d2527ad5cfa1a59d38ea758a795b /labs/fs1.html | |
| parent | e61377bf8a046bb216f768f2df6c76fe06a477e4 (diff) | |
| download | xv6-labs-a9953236cc9f1befb625575671bc39f1ab254bf0.tar.gz xv6-labs-a9953236cc9f1befb625575671bc39f1ab254bf0.tar.bz2 xv6-labs-a9953236cc9f1befb625575671bc39f1ab254bf0.zip | |
x
Diffstat (limited to 'labs/fs1.html')
| -rw-r--r-- | labs/fs1.html | 19 |
1 files changed, 10 insertions, 9 deletions
diff --git a/labs/fs1.html b/labs/fs1.html index 27a2b1a..45d3e0c 100644 --- a/labs/fs1.html +++ b/labs/fs1.html @@ -181,15 +181,16 @@ add <tt>$(QEMUEXTRA)</tt> to the end of <tt>QEMUOPTS</tt>. <h2>umount</h2> <p>Once your kernel passes usertests and test0 of mounttest, implement - umount. The main challenge is mount should fail if the file system - is still in use; that is, if there is an inode on the mounted device - that has a <tt>ref > 0</tt>. Furthermore, this test and unmounting - should be a atomic operation. (Hint: lock the inode cache.) Make - sure your kernel can pass test1 of mounttest. - -<p>Test2 of mounttest stresses <namex> more; if you have done - everything right above, your kernel may be able to pass it. Test3 - tests concurrent mount/unmounts with file creation. + umount. The main challenge is that umount of a file system should + fail if the file system is still in use; that is, if there is an + inode on the mounted device that has a <tt>ref > 0</tt>. + Furthermore, this test and unmounting should be an atomic + operation. (Hint: lock the inode cache.) Make sure your kernel + passes test1 of mounttest. + +<p>Test2 of mounttest stresses <tt>namex</tt> more; if you have done + everything right above, your kernel should pass it. Test3 tests + concurrent mount/unmounts with file creation. <h2>crash safety</h2> |