lkml.org 
[lkml]   [2004]   [Sep]   [25]   [last100]   RSS Feed
Views: [more markup]  [less markup]  [headers]  [forward] 
 
Messages in this thread
/
FromGabriel Paubert <>
DateSat, 25 Sep 2004 10:04:27 +0200
SubjectRe: ESP corruption bug - what CPUs are affected?
On Fri, Sep 24, 2004 at 11:43:30PM +0200, Petr Vandrovec wrote:
> On Sat, Sep 25, 2004 at 12:36:15AM +0400, Stas Sergeev wrote:
> > Hi,> > > > Petr Vandrovec wrote:> > >In that new patch I set the const to 0xe00, which> > >is 3,5K. Is it still the limitation? I can probably
> > >For 4KB stacks 2KB looks better> > OK, done that. Wondering though, for what?> > I don't need 2K myself, I need 24 bytes only.> > So what prevents me to raise the gap to 3.5K> > or somesuch? Why 2K looks better?> > You run with ESP decreased by 2KB for some time during
> CPL1 stack setup.  As you run in this part at CPL0> with same setup as on CPL1, I think that you should
> offer same stack for setup code, and for CPL1 code,
> and so each should get 2KB.

Maybe I miss something, but it seems that lret (or retl)
is not affected by this bug. What prevents you from reordering
the stack (doing the inverse operation of what the lcall7 entry
point does) and then doing:

	popfl
	lret

Yes, I see issues with debugging (trap flag mostly) but I believe
that they are solvable.

	Regards,
	Gabriel

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:06    [from the cache]
©2003-2008