crash when calling madvise( MADV_WILLNEED )

[John S. J. Anderson]

--Boundary_(ID_E6wweEjzjUI0hlnPwQEnYA)
Content-type: TEXT/PLAIN
Content-transfer-encoding: 7BIT

  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. 

--Boundary_(ID_E6wweEjzjUI0hlnPwQEnYA)
Content-type: message/external-body; access-type=local-file;
 name*=us-ascii''~%2ftmp%2fmadvise_test.c

Content-Type: text/x-csrc
Content-ID: <[e-mail]>
Content-Transfer-Encoding: binary

--Boundary_(ID_E6wweEjzjUI0hlnPwQEnYA)
Content-type: message/external-body; access-type=local-file;
 name*=us-ascii''~%2ftmp%2fopps

Content-Type: text/plain
Content-ID: <[e-mail]>
Content-Transfer-Encoding: binary

--Boundary_(ID_E6wweEjzjUI0hlnPwQEnYA)
Content-type: TEXT/PLAIN
Content-transfer-encoding: 7BIT

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

--Boundary_(ID_E6wweEjzjUI0hlnPwQEnYA)--