From: Kirill Korotaev <dev@sw.ru>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [announce, patch] 4G/4G split on x86, 64 GB RAM (and more) support
Date: Wed, 9 Jul 2003 19:17:35 +0400 [thread overview]
Message-ID: <200307091917.35500.dev@sw.ru> (raw)
In-Reply-To: <20030709164852.523093a3.ak@suse.de>
> I added a printf for the actual stack
> thread_self=4000
> my stack 0xbffff4df
> attr_init stack=00000000, stack_size=001FF000
> That's the output for pthread_attr_init. The manpage says it should fill in
> the default values and a 0 base is not that unreasonable for it.
0 is ok, the problem is in get_stackaddr.
> stack rlimit=1ff000
> thread=4000, stack=40035480, stack_size=40035480
> For the main() thread it's wrong.
exactly! For the main thread pthread_get_stackaddr returns a bull shit always
:(
But at least java 1.3 has workaround inside and handles this magic value
separatly and doesn't crash whis 3/1GB split (this value depends on TASK_SIZE
or more preciesly on current stack value aligned to some big boundary (AFAIR,
1GB)).
Anyway it's definietly a bug. I have a fix in a preloading .so library for
glibc which overrides pthread_getstack_addr symbol. If you wish I can send it
to you.
> my stack 0xbf7ffaab
> attr_init stack=00000000, stack_size=001FF000
> stack rlimit=1ff000
> thread=4002, stack=BF800000, stack_size=001FF000
>
> For the others everything is correct.
true.
[skip]
Kirill
next prev parent reply other threads:[~2003-07-09 14:54 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E19aCeB-000ICs-00.kksx-mail-ru@f23.mail.ru.suse.lists.linux.kernel>
2003-07-09 12:44 ` [announce, patch] 4G/4G split on x86, 64 GB RAM (and more) support Andi Kleen
[not found] ` <200307091851.33438.dev@sw.ru>
[not found] ` <20030709164852.523093a3.ak@suse.de>
2003-07-09 15:17 ` Kirill Korotaev [this message]
2003-07-09 10:58 "Kirill Korotaev"
2003-07-09 15:14 ` Ingo Molnar
2003-07-10 10:50 ` Kirill Korotaev
2003-07-10 10:59 ` Ingo Molnar
2003-07-10 11:35 ` Russell King
2003-07-10 12:33 ` Kirill Korotaev
2003-07-14 20:24 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2003-07-08 22:45 Ingo Molnar
2003-07-08 22:45 ` Ingo Molnar
2003-07-09 1:29 ` William Lee Irwin III
2003-07-09 1:29 ` William Lee Irwin III
2003-07-09 5:13 ` Martin J. Bligh
2003-07-09 5:13 ` Martin J. Bligh
2003-07-09 5:19 ` William Lee Irwin III
2003-07-09 5:19 ` William Lee Irwin III
2003-07-09 5:43 ` William Lee Irwin III
2003-07-09 5:43 ` William Lee Irwin III
2003-07-12 23:58 ` Davide Libenzi
2003-07-13 0:11 ` William Lee Irwin III
2003-07-13 8:13 ` jw schultz
2003-07-09 6:42 ` Ingo Molnar
2003-07-09 6:42 ` Ingo Molnar
2003-07-09 5:16 ` Dave Hansen
2003-07-09 5:16 ` Dave Hansen
2003-07-09 7:08 ` Geert Uytterhoeven
2003-07-09 7:08 ` Geert Uytterhoeven
2003-07-10 1:36 ` Martin J. Bligh
2003-07-10 1:36 ` Martin J. Bligh
2003-07-10 13:36 ` Martin J. Bligh
2003-07-10 13:36 ` Martin J. Bligh
2003-07-13 22:05 ` Petr Vandrovec
2003-07-13 22:05 ` Petr Vandrovec
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=200307091917.35500.dev@sw.ru \
--to=dev@sw.ru \
--cc=ak@suse.de \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.