From: Dave Jones <davej@redhat.com>
To: Jiri Slaby <jslaby@suse.cz>
Cc: trinity@vger.kernel.org
Subject: Re: trinity: lots of free(): invalid pointer
Date: Mon, 20 Jan 2014 16:37:59 -0500 [thread overview]
Message-ID: <20140120213759.GA11834@redhat.com> (raw)
In-Reply-To: <52DD7E2E.7000307@suse.cz>
On Mon, Jan 20, 2014 at 08:51:10PM +0100, Jiri Slaby wrote:
> (gdb) l * 0x410fa4
> 0x410fa4 is in post_modify_ldt (syscalls/modify_ldt.c:62).
> 57
> 58 ptr = (void *) shm->scratch[childno];
> 59
> 60 if (ptr != NULL)
> 61 free(ptr);
> 62 }
> 63
> 64 struct syscallentry syscall_modify_ldt = {
> 65 .name = "modify_ldt",
> 66 .num_args = 3,
>
That syscall should probably be marked as AVOID for now, as it's pretty easy
to completely screw up the LDT and segv. We'll need to be a bit more
creative to make it actually find bugs.
Dave
prev parent reply other threads:[~2014-01-20 21:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 22:37 trinity: lots of free(): invalid pointer Jiri Slaby
2014-01-17 19:09 ` Dave Jones
2014-01-20 19:31 ` Jiri Slaby
2014-01-20 19:51 ` Jiri Slaby
2014-01-20 21:37 ` Dave Jones [this message]
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=20140120213759.GA11834@redhat.com \
--to=davej@redhat.com \
--cc=jslaby@suse.cz \
--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;
as well as URLs for NNTP newsgroup(s).