Re: 2.6.12-rc5-mm1 alsa oops

[Andrew Morton <akpm@osdl.org>]

Wolfgang Wander <wwc@rentec.com> wrote:
>
> Lee Revell wrote:
> > On Thu, 2005-05-26 at 20:12 +0200, Borislav Petkov wrote:
> > 
> >>On Thursday 26 May 2005 20:01, Lee Revell wrote:
> >>
> >>>On Thu, 2005-05-26 at 19:44 +0200, Borislav Petkov wrote:
> >>>
> >>>><snip>
> >>>>
> >>>>Andrew,
> >>>>
> >>>>similar oopses as the one I'm replying to all over the place. At it
> >>>>happens m in snd_pcm_mmap_data_close(). Here's a stack trace:
> >>>
> >>>No one using ALSA CVS or any of the 1.0.9 release candidates ever
> >>>reported this, but lots of -mm users are... does that help at all?  I
> >>>suspect some upstream bug that ALSA just happens to trigger.
> >>
> >>yeah,
> >>
> >>this has to do with alsa indirectly. snd_pcm_mmap_data_close() accesses some 
> >>vm_area_struct->vm_private_data and apparently there have been some 
> >>optimizations to mmap code to avoid fragmentation of vma's so i think there's 
> >>the problem. However, we'll need the smarter ones here :))
> > 
> > 
> > Any idea which patches to back out?
> 
> 
> avoiding-mmap-fragmentation-fix-2.patch
> 
> seems to do the trick. Ken will likely have a fix-3 shortly ;-)
> 

Yup.  This appears to be not-an-alsa-bug.  Thanks.