public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Janne Heikkinen <jamse@sci.fi>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.20 oopses with OSS/munmap
Date: Wed, 19 Feb 2003 19:28:00 +0200	[thread overview]
Message-ID: <3E53BEA0.8000808@sci.fi> (raw)
In-Reply-To: <3E532DE8.1080303@sci.fi>

Janne Heikkinen wrote:

> When trying to to use mmap with OSS with kernel version 2.4.20, 
> program causes oops
> when munmapping takes place (either when calling munmap directly or 
> when program is
> terminating).  

I looked into it more carefully and most of the time I don't actually 
get oops but system
just goes unstable. It is allways second time when program is run when 
this hang with
munmap() happens.

Program that causes this maps DMA buffer with mmap, uses SNDCTL_DSP_GETIPTR
ioctl() after select()  and then copies data from mmap'd buffer into 
another buffer. Everything
goes fine until munmap().

It seems to be exactly the same problem that Paul Forgey had run into 
and wrote
about in January with subject "oss bug introduced since 2.4.18?".

Janne Heikkinen


      reply	other threads:[~2003-02-19 17:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-19  7:10 2.4.20 oopses with OSS/munmap Janne Heikkinen
2003-02-19 17:28 ` Janne Heikkinen [this message]

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=3E53BEA0.8000808@sci.fi \
    --to=jamse@sci.fi \
    --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