mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Joe Duarte <songofapollo@gmail.com>
To: musl@lists.openwall.com
Subject: Re: Formal verification of MUSL
Date: Mon, 11 Apr 2016 18:00:24 -0700	[thread overview]
Message-ID: <CAESemU8-1HKdvmwKs4XeLyDPBWwFGjn0QRhs75C6+MeF8oB9aw@mail.gmail.com> (raw)
In-Reply-To: <CAKi8BVPf+u6wg-DFGr6VTzgMWUo6dtr+gSaG1MU4Orzg43LYbA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2211 bytes --]

>
> >
> > I have registered
> >
> > https://scan.coverity.com/projects/libc-musl
>
> "You are not authorized to access this page."
> I have no experience with Coverity, but I guess you missed a step to make
> it public. (The search also comes up empty.)
>

​Yes, I noticed that as well. It gave me the same "not authorized" message.
Normally, we should be able to add the project to our personal Coverity
accounts by going to My Dashboard (top), click the Add a New Project
button, then search for the project. Currently, musl is still not showing
up in the search – maybe it takes a couple of days to show?

Nagy, everything you said sounds right. What about unikernels? Long-term,
I'm more interested in running unikernels than in running Linux, BSD, or
Windows. I'm thinking of something lik
e OSv
​, where they built an ELF linker from scratch, as well as implementing the
Linux system calls:
https://github.com/cloudius-systems/osv/wiki/Components-of-OSv

In their case, they were going for glibc compatibility, and I assume a
straight musl implementation would be easier. This ultimately gets at the
separation of OS syscalls and ABIs vs. the libc. What if I have an OS or
unikernel that doesn't know anything about C or POSIX, where C isn't a
first-class citizen so much as an honored guest? musl-leveraging C
applications would presumably be statically compiled in that case (and
perhaps containerized), but there would also need be an ABI layer that is
unclear to me. (Maybe this is relevant: How to Run POSIX Apps in a Minimal
Picoprocess: http://research.microsoft.com/apps/pubs/default.aspx?id=183461
-- which they might be drawing from in their recently announced bash or
Ubuntu support. How they emulated the Linux ABI in that paper is very
interesting.)

I think the formal verification task would be simplified if we could shrink
the ABI down in a unikernel or similar context, but I've only just begun to
think about this.

On floating point, the C
ompCert team just published a new paper on verified compilation of floating
point computations:
​ ​
https://hal.inria.fr/hal-00862689
​  ​
It looks like nice work.

Cheers,

Joe

[-- Attachment #2: Type: text/html, Size: 4183 bytes --]

  reply	other threads:[~2016-04-12  1:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-11  2:18 Joe Duarte
2016-04-11  4:23 ` Rich Felker
2016-04-11  4:35   ` Khem Raj
2016-04-11 15:55     ` Eric Engeström
2016-04-12  1:00       ` Joe Duarte [this message]
2016-04-12  2:47         ` Isaac Dunham
2016-05-02  0:35       ` Joe Duarte
2016-04-11 12:21   ` Szabolcs Nagy

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=CAESemU8-1HKdvmwKs4XeLyDPBWwFGjn0QRhs75C6+MeF8oB9aw@mail.gmail.com \
    --to=songofapollo@gmail.com \
    --cc=musl@lists.openwall.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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).