From: Jean-Marc Saffroy <saffroy@gmail.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: oops in :snd_pcm_oss:resample_expand+0x19c/0x1f0
Date: Sun, 24 Sep 2006 21:05:09 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0609242018150.4838@erda.mds> (raw)
In-Reply-To: <260d3bff0609241104o65218c3bwc59aef94eddbca53@mail.gmail.com>
On Sun, 24 Sep 2006, Jean-Marc Saffroy wrote:
> On Sun, 2006-09-24 at 19:01 +0200, Jean-Marc Saffroy wrote:
>> Yes yes, I know the kernel is tainted "P" (courtesy of the infamous
>> Nvidia module), so flame me if you want, but some investigation leads
>> me to think it could be an issue in core kernel modules, so read on if
>> you still want the gory details. ;-)
>
> Please don't post tainted Oops reports to LKML. It's not a political
> issue, it's a technical one - a tainted kernel CANNOT be debugged.
Thank you for flaming. ;-) I thought the lines above would lead some
people to read on and post an enlightening answer to the implicit question
that followed, so I'll restate it below.
> Reproduce with an untainted kernel and repost.
Ok, I'll try.
In the mean time, maybe someone can try to answer my original question,
that was: is there a race between snd_pcm_oss_change_params() reallocating
a buffer and resample_expand() using another (possibly the same)?
Now I hope that my mail client does not taint the question as well. ;-)
Cheers,
--
saffroy@gmail.com
next prev parent reply other threads:[~2006-09-24 19:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-24 17:01 Jean-Marc Saffroy
2006-09-24 17:39 ` Lee Revell
[not found] ` <260d3bff0609241104o65218c3bwc59aef94eddbca53@mail.gmail.com>
2006-09-24 19:05 ` Jean-Marc Saffroy [this message]
2006-09-24 20:54 ` Andrew Morton
2006-09-24 22:03 ` Jean-Marc Saffroy
2006-09-25 15:30 ` Vivek Goyal
2006-09-25 21:01 ` Jean-Marc Saffroy
2006-09-25 23:37 ` Vivek Goyal
2006-09-26 0:59 ` Jean-Marc Saffroy
2006-09-27 14:38 ` 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=Pine.LNX.4.64.0609242018150.4838@erda.mds \
--to=saffroy@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®