public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: jacobs@genehack.org (John S. J. Anderson)
To: linux-kernel@vger.kernel.org
Subject: crash when calling madvise( MADV_WILLNEED )
Date: Thu, 12 Dec 2002 18:03:36 -0500	[thread overview]
Message-ID: <87d6o64z7b.fsf@mendel.genehack.org> (raw)

[-- Attachment #1: Type: TEXT/PLAIN, Size: 816 bytes --]


  A developer that I support has discovered that the attached code is
  capable of crashing many late series 2.4.x kernels, including
  2.4.20. The easiest way to reproduce this crash is to compile the
  attached code, and call it via 'madvise_test 3 FILE', where FILE is
  a data file of at least 1.5 GB. The contents of FILE don't seem to
  matter. The crash may happen more quickly if multiple copies of the
  program are started. Sometimes the process locks up the terminal it
  is running in; sometimes the kernel throws an OPPS and the whole
  machine goes down. There doesn't seem to be a pattern as to which
  event happens when. 

  This has been observed on both a Dell 8450 (8 CPU, 8 gig RAM) and a
  Dell 1650 (2 CPU, 2 gig RAM). I've also included an oops that we
  captured.

  Thanks for any help. 


[-- Attachment #2: ~/tmp/madvise_test.c --]
[-- Type: message/external-body, Size: 111 bytes --]

[-- Attachment #3: ~/tmp/opps --]
[-- Type: message/external-body, Size: 110 bytes --]

[-- Attachment #4: Type: TEXT/PLAIN, Size: 256 bytes --]



john.
-- 
"[L]iberty of the press is the right of the lonely pamphleteer who
uses carbon paper or a mimeograph just as much as of the large
metropolitan publisher who utilizes the latest photocomposition
methods."- judge's decision in Branzburg v. Hayes

                 reply	other threads:[~2002-12-12 22:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87d6o64z7b.fsf@mendel.genehack.org \
    --to=jacobs@genehack.org \
    --cc=linux-kernel@vger.kernel.org \
    /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