public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stas Sergeev <stsp@aknet.ru>
To: Alexander Nyberg <alexn@telia.com>
Cc: Andrew Morton <akpm@osdl.org>,
	torvalds@osdl.org, Mateusz Berezecki <mateuszb@gmail.com>,
	linux-kernel@vger.kernel.org, zwane@arm.linux.org.uk
Subject: Re: 2.6.12-rc3 OOPS  in vanilla source (once more)
Date: Wed, 04 May 2005 07:45:33 +0400	[thread overview]
Message-ID: <4278455D.308@aknet.ru> (raw)
In-Reply-To: <1115120050.945.39.camel@localhost.localdomain>

Hello.

Alexander Nyberg wrote:
> /From my reading a task that is scheduled away cannot have a partial/
> saved pt_regs. If this is correct then ptrace won't suffer from this
> problem
This is most likely correct, I
just wanted to be sure.

> I need to look at the partial stack issue closer, don't think I fully
> understand it yet.
When the IRQ/NMI interrupts the
ring0 code (kernel), since the
handler is also ring0, the interrupt
gate doesn't save the SS and ESP
when switching, so you miss the 8 bytes.
After looking at the code again I
don't think this can affect the
ptrace since the ptrace probably
never traces from an IRQ context
(I hope).
So I think it is safe to ignore my
previous comment. (if only perhaps
the "optimized" version of the patch
is to have a look)


  parent reply	other threads:[~2005-05-04  3:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-02 14:04 2.6.12-rc3 OOPS in vanilla source (once more) Mateusz Berezecki
2005-05-03  3:05 ` Andrew Morton
2005-05-03 11:34   ` Alexander Nyberg
2005-05-03 17:20     ` Stas Sergeev
2005-05-03 23:45       ` Alexander Nyberg
2005-05-04  3:45     ` Stas Sergeev [this message]
2005-05-08 23:12     ` Mateusz Berezecki

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=4278455D.308@aknet.ru \
    --to=stsp@aknet.ru \
    --cc=akpm@osdl.org \
    --cc=alexn@telia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mateuszb@gmail.com \
    --cc=torvalds@osdl.org \
    --cc=zwane@arm.linux.org.uk \
    /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