From: Kaoru Esashika <e_kaoru5@yahoo.co.jp>
To: gentoo-soc@lists.gentoo.org
Subject: [gentoo-soc] Weekly Report: Fusebox - FUSE Porwered sandbox project
Date: Mon, 6 Jul 2020 11:10:12 +0900 [thread overview]
Message-ID: <CAHuS14PA79hxsybDzj_F5SKpSArEiGF8eAz9L4Gsi=oxPG0CbA@mail.gmail.com> (raw)
Hi,
This week, I'm trying to fix some issue which is pointed out by my
mentor (thanks!)
Some of the issues are caused by deadlock. Since Fusebox is a single
thread program,
It cannot process a request from VFS (kernel) while processing another request.
So I choose a solution that hides the directory which causes deadlock.
Because Fusebox has been developed for sandbox, basically it doesn't
need recursive access.
So I think this not bad.
In the next week, I will write unit test because debugging and testing
burden me.
And also I will implement virtual inode mechanism (which will kick out
a compromise in the code)
Project Repository: https://github.com/pluser/fusebox
Regards,
Kaoru Esashika
next reply other threads:[~2020-07-06 2:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 2:10 Kaoru Esashika [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-08-24 9:55 [gentoo-soc] Weekly Report: Fusebox - FUSE Porwered sandbox project Kaoru Esashika
2020-08-17 8:27 Kaoru Esashika
2020-08-09 23:00 Kaoru Esashika
2020-08-02 23:00 Kaoru Esashika
2020-07-26 23:00 Kaoru Esashika
2020-07-27 4:48 ` EBo
2020-07-28 20:08 ` Kaoru Esashika
2020-07-28 20:24 ` EBo
2020-07-19 23:00 Kaoru Esashika
2020-07-12 23:00 Kaoru Esashika
2020-06-28 18:47 Kaoru Esashika
2020-06-21 11:17 Kaoru Esashika
2020-06-21 18:21 ` Michał Górny
2020-06-22 16:17 ` Kaoru Esashika
2020-06-22 18:02 ` Michał Górny
2020-06-14 11:41 Kaoru Esashika
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHuS14PA79hxsybDzj_F5SKpSArEiGF8eAz9L4Gsi=oxPG0CbA@mail.gmail.com' \
--to=e_kaoru5@yahoo.co.jp \
--cc=gentoo-soc@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox