From: Denis Vlasenko <vda@ilport.com.ua>
To: Tomasz Malesinski <tmal@mimuw.edu.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Segfault on the i386 enter instruction
Date: Fri, 12 May 2006 16:47:36 +0300 [thread overview]
Message-ID: <200605121647.36916.vda@ilport.com.ua> (raw)
In-Reply-To: <20060512131654.GB2994@duch.mimuw.edu.pl>
On Friday 12 May 2006 16:16, Tomasz Malesinski wrote:
> The code attached below segfaults on the enter instruction. It works
> when a stack frame is created by the three commented out
> instructions and also when the first operand of the enter instruction
> is small (less than about 6500 on my system).
>
> AFAIK, the only difference between creating a stack frame with the
> enter instruction or push/mov/sub is that enter checks if the new
> value of esp is inside the stack segment limit.
>
> I tested it on a vanilla kernel 2.4.26 on Intel Celeron and also on
> probably non-vanilla 2.6.16.13 running on 3 dual core AMD Opteron,
> quite busy, server. It is working in 32-bit mode. Interestingly, on
> the second machine sometimes the program worked correctly.
Does not segfault for me:
# gcc Segfault.S
# ./a.out
asdf
# cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 11
model name : Intel(R) Celeron(TM) CPU 1200MHz
stepping : 1
cpu MHz : 1196.201
cache size : 256 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse
bogomips : 2395.77
# gcc -v 2>&1 | tail -1
gcc version 3.4.3
--
vda
--
vda
next prev parent reply other threads:[~2006-05-12 13:48 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-12 13:16 Segfault on the i386 enter instruction Tomasz Malesinski
2006-05-12 13:47 ` Denis Vlasenko [this message]
2006-05-12 13:50 ` Andi Kleen
2006-05-12 14:03 ` Denis Vlasenko
2006-05-12 15:31 ` Tomasz Malesinski
2006-05-15 11:36 ` Bart Hartgers
2006-05-15 11:46 ` Andi Kleen
2006-05-15 13:36 ` linux-os (Dick Johnson)
2006-05-15 14:19 ` Bart Hartgers
2006-05-12 14:07 ` linux-os (Dick Johnson)
2006-05-12 14:20 ` Denis Vlasenko
2006-05-12 14:42 ` linux-os (Dick Johnson)
2006-05-12 14:53 ` Denis Vlasenko
2006-05-15 20:53 ` Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2006-05-14 17:56 Stas Sergeev
2006-05-15 7:40 ` Andi Kleen
2006-05-15 17:15 ` Stas Sergeev
2006-05-15 18:44 ` Andi Kleen
2006-05-15 19:38 ` Stas Sergeev
2006-05-15 19:56 ` Lee Revell
2006-05-15 22:49 ` Ingo Oeser
2006-05-15 22:56 ` Lee Revell
2006-05-16 2:29 Chuck Ebbert
2006-05-16 9:32 ` Andi Kleen
2006-05-17 8:20 Chuck Ebbert
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=200605121647.36916.vda@ilport.com.ua \
--to=vda@ilport.com.ua \
--cc=linux-kernel@vger.kernel.org \
--cc=tmal@mimuw.edu.pl \
/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