public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark J Roberts <mjr@znex.org>
To: linux-kernel@vger.kernel.org
Subject: Framebuffer, mmap(), hanging in D state, root FS unmount failure.
Date: Thu, 27 Dec 2001 13:50:37 -0600	[thread overview]
Message-ID: <20011227195037.GA229@znex> (raw)

#include <assert.h>
#include <sys/mman.h>
#include <fcntl.h>
int main(void)
{
	char *p;
	assert((p = mmap(0, 1, PROT_READ|PROT_WRITE, MAP_SHARED, open("/dev/fb/0", O_RDWR), 0)) != MAP_FAILED);
	p[4096] = 0; /* this hangs */
	return 0;
}

When I run this on my 2.4.17rc2aa2 kernel with a Voodoo3000
framebuffer, the process hangs forever in D state. ps and top will
then hang the same way when they read the /proc/pid files for the
hung process. And my root filesystem won't unmount.

It only happens when PROT_READ|PROT_WRITE is specified - when I use
only PROT_WRITE, the program segfaults like you'd expect.... but
once the PROT_READ|PROT_WRITE version has hung, PROT_WRITE-only
versions will also hang.

             reply	other threads:[~2001-12-27 19:44 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-27 19:50 Mark J Roberts [this message]
2001-12-29  0:23 ` Framebuffer, mmap(), hanging in D state, root FS unmount failure Andrew Morton
2001-12-30  8:34   ` [patch] " Andrew Morton
2001-12-30 21:13     ` [patch] Re: Framebuffer...Why oh Why??? Timothy Covell
     [not found]       ` <3C2F8727.5D4AAE21@zip.com.au>
2001-12-30 22:27         ` Timothy Covell
2001-12-31  1:51           ` James Simmons
2001-12-31  2:49             ` Andrew Morton
2001-12-31  3:23               ` James Simmons
2001-12-31 12:07               ` Geert Uytterhoeven
2001-12-31 13:18                 ` Alan Cox
2001-12-31 21:53                   ` Oliver Xymoron
2001-12-31  0:19       ` Linus Torvalds
2001-12-31  1:54         ` [Linux-fbdev-devel] " James Simmons
2001-12-31  8:03         ` gmack
2001-12-31  9:05         ` Benjamin Herrenschmidt
2001-12-31 21:41         ` Rob Landley
2002-01-01  7:00           ` Werner Puschitz
2002-01-03 22:26             ` Marco Ermini
2002-01-04 13:27               ` [OT] " Tommi Kyntola
2002-01-04 14:04                 ` Marco Ermini
2002-01-01  7:00           ` Timothy Covell
2002-01-01 10:42             ` Alan Cox
2002-01-01 20:36               ` Rob Landley
2002-01-02 11:36               ` Daniel Phillips
2002-01-01 14:31           ` Marius Gedminas
2001-12-31 21:42         ` Scott McDermott
2001-12-31 21:56           ` Arnaldo Carvalho de Melo
2001-12-31 22:26             ` James Simmons
2001-12-31 22:31               ` Arnaldo Carvalho de Melo
2002-01-01  2:43                 ` Bill Nottingham
2002-01-01  6:15                   ` Arnaldo Carvalho de Melo
2002-01-01 18:42                   ` Joachim Steiger
2002-01-01 10:21                 ` Alan Cox
2002-01-01  0:23         ` Ken Moffat
2002-01-01  7:03           ` Timothy Covell
2001-12-31 12:10       ` Geert Uytterhoeven

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=20011227195037.GA229@znex \
    --to=mjr@znex.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