From: "Abel Bernabeu" <abel.bernabeu@gmail.com>
To: "Pavel Machek" <pavel@ucw.cz>, linux-kernel@vger.kernel.org
Subject: Re: Fwd: brk randomization breaks columns
Date: Mon, 4 Feb 2008 22:54:54 +0100 [thread overview]
Message-ID: <15577be70802041354s23e5b289w56f724dfdf8c3242@mail.gmail.com> (raw)
In-Reply-To: <20080204195251.GB4915@elf.ucw.cz>
2008/2/4, Pavel Machek <pavel@ucw.cz>:
> > >
> > > > I still don't seem to fully understand what is happening here --
> > > > aparently this is triggerable only with old programs linked against
> > > > libc.so.5, and I am not able to trigger it with my trivial program when
> > > > I link it against old libc.so.5, which just basically does brk() and
> > > > checks whether /proc/<pid>/maps are OK. Seems to me that (at least
> > > > certain versions) of libc.so.5 (wrongly) assume that end of the bss is
> > > > the start of the heap, but I will try to investigate it more.
> >
> > I think I am getting the some problem with brand new binaries produced
> > by myself :(
> >
> > Look at this report I posted days ago:
> >
> > http://marc.info/?l=linux-kernel&m=120169141603789&w=2
>
> Your crash is in kernel, no? Anyway, I can workaround mine by
> disabling randomization...
Yes, my crash happens at kernel space, but is due to the randomized
params passed to set_brk (the same thing that makes your game crash
later at runtime).
I did not understand why my kernel was crashing before reading your
comments, but now I think is all happening because of the brk
randomization. Sorry, I will not be able to try disabling
randomization until tomorrow at office in order to confirm you this.
I am trying to figure out what is relation the brk randomization
feature and my crash... but makes sense to me now, trying to find it.
Yours, Abel.
next prev parent reply other threads:[~2008-02-04 21:55 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-04 12:28 Pavel Machek
2008-02-04 13:01 ` Ingo Molnar
2008-02-04 13:28 ` Pavel Machek
2008-02-04 14:55 ` Jiri Kosina
2008-02-04 20:25 ` Pavel Machek
2008-02-04 14:33 ` Jiri Kosina
2008-02-04 16:12 ` Jiri Kosina
[not found] ` <15577be70802041016m97cddbfk43b9073408bcbce9@mail.gmail.com>
[not found] ` <15577be70802041029o2975ba6do34589bbdc81d1652@mail.gmail.com>
2008-02-04 19:52 ` Fwd: " Pavel Machek
2008-02-04 21:54 ` Abel Bernabeu [this message]
2008-02-04 22:48 ` Jiri Kosina
2008-02-04 23:13 ` Abel Bernabeu
2008-02-04 23:39 ` Pavel Machek
2008-02-04 20:31 ` Pavel Machek
2008-02-05 1:57 ` Jiri Kosina
2008-02-05 11:06 ` [regression] " Pavel Machek
2008-02-05 12:50 ` Jiri Kosina
2008-02-05 12:54 ` Ingo Molnar
2008-02-05 13:05 ` Jakub Jelinek
2008-02-05 16:18 ` Pavel Machek
2008-02-05 16:37 ` Ingo Molnar
2008-02-05 16:12 ` Pavel Machek
2008-02-05 13:08 ` Hugh Dickins
2008-02-05 15:00 ` Arjan van de Ven
2008-02-05 15:46 ` Pavel Machek
2008-02-05 15:49 ` Jiri Kosina
2008-02-05 15:55 ` Pavel Machek
2008-02-05 15:49 ` Ingo Molnar
2008-02-05 15:59 ` Pavel Machek
2008-02-05 16:06 ` Ingo Molnar
2008-02-05 22:03 ` Pavel Machek
2008-02-05 16:58 ` Arjan van de Ven
2008-02-05 17:33 ` Pavel Machek
2008-02-05 22:35 ` Jiri Kosina
2008-02-06 3:24 ` Randy Dunlap
2008-02-05 16:02 ` Pavel Machek
2008-02-05 16:09 ` Ingo Molnar
2008-02-05 22:04 ` Pavel Machek
2008-02-05 18:05 ` Pavel Machek
2008-02-05 20:42 ` Jiri Kosina
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=15577be70802041354s23e5b289w56f724dfdf8c3242@mail.gmail.com \
--to=abel.bernabeu@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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
all inboxes | Powered by JetHome®