From a9953236cc9f1befb625575671bc39f1ab254bf0 Mon Sep 17 00:00:00 2001 From: Frans Kaashoek Date: Sat, 17 Aug 2019 12:52:25 -0400 Subject: [PATCH] x --- labs/fs1.html | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 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 $(QEMUEXTRA) to the end of QEMUOPTS.

umount

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 ref > 0. Furthermore, this test and unmounting - should be a atomic operation. (Hint: lock the inode cache.) Make - sure your kernel can pass test1 of mounttest. + 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 ref > 0. + Furthermore, this test and unmounting should be an atomic + operation. (Hint: lock the inode cache.) Make sure your kernel + passes test1 of mounttest. -

Test2 of mounttest stresses more; if you have done - everything right above, your kernel may be able to pass it. Test3 - tests concurrent mount/unmounts with file creation. +

Test2 of mounttest stresses namex more; if you have done + everything right above, your kernel should pass it. Test3 tests + concurrent mount/unmounts with file creation.

crash safety