From: nils.carlson@ludd.ltu.se (Nils Carlson)
Subject: [ltt-dev] [UST] malloc error found by david
Date: Thu, 30 Sep 2010 21:21:08 +0200 [thread overview]
Message-ID: <3E62D12A-B4E9-4C14-8001-55A7E39E651E@ludd.ltu.se> (raw)
In-Reply-To: <4CA3C561.3060807@polymtl.ca>
On Sep 30, 2010, at 1:01 AM, David Goulet wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
>
> On 10-09-29 04:40 PM, Mathieu Desnoyers wrote:
>> Hi Nils,
>>
>> Please double-check that you ported commit
>>
>> 38516ab59fbc5b3bb278cf5e1fe2867c70cff32e
>>
>> tracing: Let tracepoints have data passed to tracepoint callbacks
>>
>> correctly from mainline. There is at least a bug in
>>
>> static inline void *allocate_probes(int count)
>>
>> (sizeof(void *) should be changed for sizeof(struct tracepoint_func))
>
> Yes, but for UST, it's sizeof(struct probe), actually almost the
> same but
> different name :P
>
> This was introduce in UST from commit (in libust/tracepoint.c)
>
> 1dba3e6c054da18f238d051da5b1839bd5e4e4dd
>
> I really have NO idea how it came in because for that commit I only
> changed the
> malloc to zmalloc. So I think, somekind of "merge" between patches
> went wrong
> and git didn't notice. Shit happens ;)
>
Yepp. Applied fix, haven't done any digging in how it got in there.
/Nils
> Thanks
> David
>
>>
>> Hopefully no other bugs crept in.
>>
>> Credits go to David Goulet, how just spent 2 days hunting this one
>> down.
>>
>> Thanks,
>>
>> Mathieu
>>
>>
>>
>
> - --
> David Goulet
> LTTng project, DORSAL Lab.
>
> 1024D/16BD8563
> BE3C 672B 9331 9796 291A 14C6 4AF7 C14B 16BD 8563
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
>
> iEYEARECAAYFAkyjxWEACgkQSvfBSxa9hWPcUQCePVOAXil4Qi5L53XPY5sx1yH3
> U+AAoLqnA+GDQz1BM3Cp6c1rMMgq+Lcp
> =Uken
> -----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-09-30 19:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-29 13:27 [ltt-dev] [geissert@debian.org: Bug#598309: ust-bin: CVE-2010-3386: insecure library loading] Jon Bernard
2010-09-29 13:32 ` David Goulet
2010-09-29 13:47 ` Mathieu Desnoyers
2010-09-29 15:16 ` Alexandre Montplaisir
2010-09-29 15:47 ` Mathieu Desnoyers
2010-09-29 15:06 ` [ltt-dev] [PATCH UST] Fix insecure library loading (Debian Bug #598309, CVE-2010-3386) Mathieu Desnoyers
2010-09-29 16:32 ` David Goulet
2010-09-29 17:25 ` Mathieu Desnoyers
2010-09-29 18:57 ` Nils Carlson
2010-09-29 20:40 ` [ltt-dev] [UST] malloc error found by david Mathieu Desnoyers
2010-09-29 23:01 ` David Goulet
2010-09-30 19:21 ` Nils Carlson [this message]
2010-09-29 23:11 ` [ltt-dev] [PATCH UST] Fix insecure library loading (Debian Bug #598309, CVE-2010-3386) David Goulet
2010-09-30 10:18 ` Nils Carlson
2010-09-30 14:49 ` [ltt-dev] [PATCH UST] Fix insecure library loading (Debian Bug #598309, CVE-2010-3386) (v2) Mathieu Desnoyers
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=3E62D12A-B4E9-4C14-8001-55A7E39E651E@ludd.ltu.se \
--to=nils.carlson@ludd.ltu.se \
/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