From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Randy Dunlap <randy.dunlap@oracle.com>,
lkml <linux-kernel@vger.kernel.org>,
linux-next@vger.kernel.org
Subject: Re: next-20081023 x86_64 boot hang: int3
Date: Thu, 23 Oct 2008 21:57:23 +0400 [thread overview]
Message-ID: <20081023175723.GD29659@localhost> (raw)
In-Reply-To: <20081023175008.GC29659@localhost>
[Cyrill Gorcunov - Thu, Oct 23, 2008 at 09:50:08PM +0400]
...
|
| Hi Randy,
|
| i don't remember the details -- these int3 opcodes are likely to
| come from some paging or stack protector... hmm... can't remember
| absolutely :) There was a thread on LKML about half a year ago about
| why to fill pages with int3 opcode. But I may be absolutely wrong :)
|
| - Cyrill -
Hmm, I think I'm not in touch don't play attention on this mail,
sorry :)
- Cyrill -
next prev parent reply other threads:[~2008-10-23 17:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-23 17:43 next-20081023 x86_64 boot hang: int3 Randy Dunlap
2008-10-23 17:50 ` Cyrill Gorcunov
2008-10-23 17:57 ` Cyrill Gorcunov [this message]
2008-10-24 5:07 ` Hiroshi Shimamoto
2008-10-24 5:19 ` Randy Dunlap
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=20081023175723.GD29659@localhost \
--to=gorcunov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
/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;
as well as URLs for NNTP newsgroup(s).