From 87fc48ff67f74c14f3b55bae60060c5053d664d4 Mon Sep 17 00:00:00 2001 From: Guru Das Srinagesh Date: Tue, 25 Jul 2017 00:00:54 -0700 Subject: [PATCH] Add Task 20 description --- Task20/task20.txt | 37 +++++++++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 Task20/task20.txt diff --git a/Task20/task20.txt b/Task20/task20.txt new file mode 100644 index 0000000..c49d107 --- /dev/null +++ b/Task20/task20.txt @@ -0,0 +1,37 @@ +This is Task 20 of the Eudyptula Challenge +------------------------------------------ + +Networking filters turned out to be not all that complex in the end, +great work with that. + +So, here's the final task. + +There might be other tasks that get created and sent out later on, but +the original challenge had 20 tasks, so after finishing this one, you +can consider yourself done! + +Let's try something a bit harder. Something that might cause some data +loss on a filesystem, always a fun thing to play with, if for no other +reason than to not be afraid of things like that in the future. + +This task requires you to work on the fat filesystem code: + - Add an ioctl to modify the volume label of a mounted fat filesystem. + Be sure to handle both 16 and 32 bit fat filesystems {hint!} + - Provide a userspace .c program to test this new ioctl. + +That's it! Seems so simple, right? I wonder why that option isn't in +the kernel tree already... + +Anyway, provide a patch to the kernel, and the .c file used to test the +new ioctl, as well as "proof" of this working. Make sure you don't run +into 32/64bit kernel issues with the ioctl, if you do things correctly, +you shouldn't have any problems. + +I recommend doing this work on either a loop-back fat filesystem on your +"normal" filesystem, or on a USB stick. Either will work just as well, +and make things easier to debug and test. + +Watch out for locking issues, as well as dirty filesystem state +problems. + +Best of luck!