mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Anton Altaparmakov <aia21@cam.ac.uk>
To: "Dunlap, Randy" <randy.dunlap@intel.com>
Cc: "'David Woodhouse'" <dwmw2@infradead.org>,
	Linus Torvalds <torvalds@transmeta.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Brian Gerst <bgerst@didntduck.org>,
	linux-kernel@vger.kernel.org
Subject: RE: [PATCH] x86 page fault handler not interrupt safe
Date: Mon, 07 May 2001 18:52:49 +0100	[thread overview]
Message-ID: <5.1.0.14.2.20010507184618.00a8a5b0@pop.cus.cam.ac.uk> (raw)
In-Reply-To: <D5E932F578EBD111AC3F00A0C96B1E6F07DBE26F@orsmsx31.jf.intel .com>

At 18:32 07/05/2001, Dunlap, Randy wrote:
> > From: David Woodhouse [mailto:dwmw2@infradead.org]
> >
> > torvalds@transmeta.com said:
> > >  If anybody has such a beast, please try this kernel patch _and_
> > > running the F0 0F bug-producing program (search for it on the 'net -
> > > it must be out there somewhere) to verify that the code still
> > > correctly handles that case.
> >
> > Something along the lines of:
> >
> > echo "unsigned long main=0xf00fc7c8;" > f00fbug.c ; make f00fbug
>
>Yes, that's what the (SGI) program uses:
>http://lwn.net/2001/0329/a/ltp-f00f.php3

That's not quite what they do. David's SGI equivalent would be:

echo "unsigned long main=0xc8c70ff0;" > f00fbug.c ; make f00fbug

i.e. remember that ia32 is little endian.

Thanks for the link.

Best regards,

Anton


-- 
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Linux NTFS Maintainer / WWW: http://sourceforge.net/projects/linux-ntfs/
ICQ: 8561279 / WWW: http://www-stu.christs.cam.ac.uk/~aia21/


       reply	other threads:[~2001-05-07 17:52 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <D5E932F578EBD111AC3F00A0C96B1E6F07DBE26F@orsmsx31.jf.intel .com>
2001-05-07 17:52 ` Anton Altaparmakov [this message]
2001-05-07 21:58 Anton Altaparmakov
     [not found] <3AF712D5.5D712E0F@didntduck.org>
2001-05-07 21:44 ` Linus Torvalds
2001-05-07 22:10   ` Brian Gerst
2001-05-08 10:45   ` Alan Cox
2001-05-08 16:45     ` Linus Torvalds
2001-05-09 22:12       ` Brian Gerst
2001-05-07 21:53 ` Nigel Gamble
  -- strict thread matches above, loose matches on Subject: below --
2001-05-07 17:32 Dunlap, Randy
2001-05-07 17:51 ` David Woodhouse
2001-05-06  1:26 Brian Gerst
2001-05-07  0:53 ` Linus Torvalds
2001-05-07  3:54   ` Brian Gerst
2001-05-07 10:45   ` Alan Cox
2001-05-07 14:57     ` Brian Gerst
2001-05-07 15:07       ` Alan Cox
2001-05-07 17:12         ` Linus Torvalds
2001-05-07 17:27           ` David Woodhouse
2001-05-07 19:54           ` Brian Gerst
2001-05-07 20:16             ` Linus Torvalds
2001-05-07 21:37           ` Alan Cox
2001-05-07 22:52           ` Jesper Juhl
2001-05-07 18:35         ` Anton Altaparmakov
2001-05-07 16:51     ` Linus Torvalds

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=5.1.0.14.2.20010507184618.00a8a5b0@pop.cus.cam.ac.uk \
    --to=aia21@cam.ac.uk \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bgerst@didntduck.org \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@intel.com \
    --cc=torvalds@transmeta.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

all inboxes | Powered by JetHome®