From: Jan Niehusmann <jan@gondor.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Ken Moffat <zarniwhoop@ntlworld.com>,
linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: [Alsa-devel] Slab corruptions & Re: 2.6.17-rc1: Oops in sound applications
Date: Wed, 5 Apr 2006 02:28:47 +0200 [thread overview]
Message-ID: <20060405002846.GA5201@knautsch.gondor.com> (raw)
In-Reply-To: <20060404231911.GA4862@knautsch.gondor.com>
On Wed, Apr 05, 2006 at 01:19:11AM +0200, Jan Niehusmann wrote:
> ...which happens to be the commit which contains the bug you already
> mentioned. I wonder if there is a second one hidden somewhere in that
> commit, or if git-bisect led me to that bug while the second one is
> hidden in a different commit...
Well, I did some additional debugging on that, working on git version
3bf75f9b90c981f18f27a0d35a44f488ab68c8ea:
In snd_pcm_oss_release() I added
snd_assert(substream != NULL, return -ENXIO);
in front of the first access to substream->pcm, which leads to
Apr 5 02:13:13 knautsch kernel: [17180638.784000] BUG? (substream != ((void *)0))
when opening /dev/dsp for write.
If I now add the patch you suggested, correcting the check in
snd_pcm_oss_open_file(), accessing /dev/dsp instead leads to EINVAL.
So I guess git bisect really lead me to this already known bug.
Jan
next prev parent reply other threads:[~2006-04-05 0:28 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-03 21:01 2.6.17-rc1: Oops in sound applications Ken Moffat
2006-04-04 13:38 ` Slab corruptions & " Jan Niehusmann
2006-04-04 13:38 ` Jan Niehusmann
2006-04-04 15:56 ` [Alsa-devel] " Takashi Iwai
2006-04-04 17:23 ` Jan Niehusmann
2006-04-04 17:32 ` Ken Moffat
2006-04-04 17:32 ` Ken Moffat
2006-04-04 19:06 ` Jan Niehusmann
2006-04-04 19:06 ` [Alsa-devel] " Jan Niehusmann
2006-04-04 19:12 ` Takashi Iwai
2006-04-04 20:00 ` Ken Moffat
2006-04-04 20:31 ` Ken Moffat
2006-04-04 20:31 ` Ken Moffat
2006-04-04 20:00 ` Ken Moffat
2006-04-04 23:19 ` Jan Niehusmann
2006-04-04 23:19 ` [Alsa-devel] " Jan Niehusmann
2006-04-05 0:28 ` Jan Niehusmann
2006-04-05 0:28 ` Jan Niehusmann [this message]
2006-04-05 9:01 ` [Alsa-devel] " Jan Niehusmann
2006-04-05 11:14 ` Takashi Iwai
2006-04-05 11:14 ` [Alsa-devel] " Takashi Iwai
2006-04-05 12:15 ` Jan Niehusmann
2006-04-05 12:15 ` [Alsa-devel] " Jan Niehusmann
2006-04-05 12:39 ` Takashi Iwai
2006-04-05 12:56 ` Takashi Iwai
2006-04-05 12:56 ` [Alsa-devel] " Takashi Iwai
2006-04-05 12:39 ` Takashi Iwai
2006-04-05 21:19 ` Ken Moffat
2006-04-05 21:19 ` [Alsa-devel] " Ken Moffat
2006-04-05 9:01 ` Jan Niehusmann
2006-04-04 19:12 ` Takashi Iwai
2006-04-04 15:56 ` Takashi Iwai
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=20060405002846.GA5201@knautsch.gondor.com \
--to=jan@gondor.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
--cc=zarniwhoop@ntlworld.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.