public inbox for trinity@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Ildar Muslukhov <ildarm@google.com>
Cc: trinity@vger.kernel.org
Subject: Re: [PATCH] Fix syscall32 to supply 6th arg to syscal
Date: Wed, 2 Oct 2013 16:48:30 -0400	[thread overview]
Message-ID: <20131002204830.GA7803@redhat.com> (raw)
In-Reply-To: <CAEGbLttVfFEc0-LNGPYfFthQwx7j5ME38R8a4uCGa8NNWaxueQ@mail.gmail.com>

On Wed, Oct 02, 2013 at 01:44:44PM -0700, Ildar Muslukhov wrote:
 > That's what I though as well. However, just encountered segfaults on
 > x64 read syscall. Although this one might be legit.

in case you didn't realise, there's a few cases where we expect to segfault.

for eg, if we mprotect page_rand to PROT_NONE and then something tries to read it.
There's a whole bunch of similar gotchas. I've special cased the sanitise routines
of some syscalls to avoid this sort of thing, but there's a few cases where
a trinity child will corrupt itself. It then dies, and respawns, so I haven't really
worried too much about it.

	Dave

  reply	other threads:[~2013-10-02 20:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-19 21:24 [PATCH] Fix syscall32 to supply 6th arg to syscal Ildar Muslukhov
2013-09-19 21:35 ` Dave Jones
2013-10-02 15:12 ` Dave Jones
2013-10-02 16:14   ` Ildar Muslukhov
2013-10-02 16:43     ` Dave Jones
2013-10-02 18:12       ` Ildar Muslukhov
2013-10-02 18:15         ` Dave Jones
2013-10-02 20:44           ` Ildar Muslukhov
2013-10-02 20:48             ` Dave Jones [this message]
2013-10-02 20:53               ` Ildar Muslukhov
2013-10-02 20:57                 ` Dave Jones
2013-10-02 21:03                   ` Ildar Muslukhov

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=20131002204830.GA7803@redhat.com \
    --to=davej@redhat.com \
    --cc=ildarm@google.com \
    --cc=trinity@vger.kernel.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