From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: [PATCHv3 1/3] fix matching errors for overwritten registers in x86 CFI generation script
Date: Wed, 14 Oct 2015 15:51:42 -0400 [thread overview]
Message-ID: <20151014195141.GX8645@brightrain.aerifal.cx> (raw)
In-Reply-To: <CACsECNdxipHisoONGbgp8vf4z3E=MUHALUomgPOXa8tHzSq5DA@mail.gmail.com>
On Wed, Oct 14, 2015 at 09:44:50PM +0200, Alex wrote:
> On Wed, Oct 14, 2015 at 9:27 PM, Rich Felker <dalias@libc.org> wrote:
>
> > On Wed, Oct 14, 2015 at 09:23:59PM +0200, Alex wrote:
> > > On Wed, Oct 14, 2015 at 9:14 PM, Rich Felker <dalias@libc.org> wrote:
> > >
> > > > On Wed, Oct 14, 2015 at 12:21:05PM +0200, Alex wrote:
> > > > > This has been an interesting exercise so far. Is there any other arch
> > > > which
> > > > > you think it would be worthwhile to develop a CFI generation script
> > for?
> > > > It
> > > > > should be something which has enough users to avoid problems with
> > bitrot.
> > > >
> > > > CFI is probably a lot less interesting on archs where you have a
> > > > plenty registers not to need to manipulate stack frames in asm
> > > > functions, since in that case the debugger mostly works fine without
> > > > CFI. I don't know right off which of the other archs have significant
> > > > amounts of asm that adjusts the stack pointer, but you could go
> > > > through and check them. Having ABI info for them all would be helpful;
> > > > I'm pasting my draft ABI reference (which might have errors) below.
> > >
> > > Fair enough. If it's not likely to help anyone, I'll leave the CFI
> > > generation here.
> > >
> > > Another idea: are you interested in an implementation of POSIX AIO which
> > > uses the native AIO syscalls? Bad idea?
> >
> > Those syscalls have nothing at all to do with POSIX AIO. They're
> > completely different. :(
>
> The interface presented by the raw syscalls is not the POSIX AIO interface,
> but I haven't seen any reason yet why io_setup, io_submit, io_getevents,
> etc. couldn't be used to implement the POSIX AIO interface. Is there such a
> reason?
They only work on certain types of devices/files, and only when the
offset and memory source/dest meet some arbitrary alignment
requirements. And those are just the big problems. I don't see any
indication that they match the subtle behavior requirements for POSIX
AIO in any way.
Rich
next prev parent reply other threads:[~2015-10-14 19:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 11:28 Alex Dowad
2015-10-13 11:28 ` [PATCH 2/3] x86 CFI generation script recognizes when %ax, %ah, %al, etc. are overwritten Alex Dowad
2015-10-13 11:28 ` [PATCH 3/3] add CFI generation script for x86_64 Alex Dowad
2015-10-13 22:42 ` [PATCHv3 1/3] fix matching errors for overwritten registers in x86 CFI generation script Rich Felker
2015-10-14 10:21 ` Alex
2015-10-14 19:14 ` Rich Felker
2015-10-14 19:23 ` Alex
2015-10-14 19:27 ` Rich Felker
2015-10-14 19:44 ` Alex
2015-10-14 19:51 ` Rich Felker [this message]
2015-10-14 20:27 ` Alex
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=20151014195141.GX8645@brightrain.aerifal.cx \
--to=dalias@libc.org \
--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).