From: ori@eigenstate.org
To: 9front@9front.org
Subject: proving a file system
Date: Sun, 26 Apr 2020 14:15:06 -0700 [thread overview]
Message-ID: <F35F6716FC01914F54685D35B1382A8C@eigenstate.org> (raw)
So, I'm finally back to working on gefs, and I was thinking that it'd
be good to prove the invariants -- but I've got no experience with coq,
isabelle/HOL, or whatever I should be using. I'd want to prove that the
insertion/deletion/... is crash safe and concurrency safe, if I can do
that sanely.
Currently a little ways off from getting something that needs proving,
but curious if you think this would be worthwhile, and if you'd have
some interest in helping out.
next reply other threads:[~2020-04-26 21:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-26 21:15 ori [this message]
2020-04-26 21:57 ` [9front] " ori
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=F35F6716FC01914F54685D35B1382A8C@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.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;
as well as URLs for NNTP newsgroup(s).