From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: "'Andrew Morton'" <akpm@osdl.org>, "Wolfgang Wander" <wwc@rentec.com>
Cc: <rlrevell@joe-job.com>, <petkov@uni-muenster.de>,
<pharon@gmail.com>, <linux-kernel@vger.kernel.org>,
<alsa-devel@lists.sourceforge.net>
Subject: RE: 2.6.12-rc5-mm1 alsa oops
Date: Fri, 27 May 2005 09:42:38 -0700 [thread overview]
Message-ID: <200505271642.j4RGgbg03476@unix-os.sc.intel.com> (raw)
In-Reply-To: <20050526142444.01363443.akpm@osdl.org>
Andrew Morton wrote on Thursday, May 26, 2005 2:25 PM
> > >>
> > >>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.
I'm the guilty one here. avoiding-mmap-fragmentation-fix-2.patch has
a major clash using vm_private_data where alsa is also using. I just
posted a patch, please try that out. Thanks.
http://marc.theaimsgroup.com/?l=linux-mm&m=111721191501940&w=2
- Ken
next prev parent reply other threads:[~2005-05-27 16:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-26 7:32 2.6.12-rc5-mm1 alsa oops Islam Amer
2005-05-26 17:44 ` Borislav Petkov
2005-05-26 18:01 ` Lee Revell
2005-05-26 18:12 ` Borislav Petkov
2005-05-26 18:32 ` Lee Revell
2005-05-26 18:35 ` Wolfgang Wander
2005-05-26 18:59 ` Lawrence Walton
2005-05-26 21:24 ` Andrew Morton
2005-05-27 16:42 ` Chen, Kenneth W [this message]
2005-05-28 9:10 ` Borislav Petkov
[not found] ` <4296100F.2090202@rentec.com>
2005-05-26 18:33 ` Islam Amer
-- strict thread matches above, loose matches on Subject: below --
2005-05-26 18:42 Colin Harrison
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=200505271642.j4RGgbg03476@unix-os.sc.intel.com \
--to=kenneth.w.chen@intel.com \
--cc=akpm@osdl.org \
--cc=alsa-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=petkov@uni-muenster.de \
--cc=pharon@gmail.com \
--cc=rlrevell@joe-job.com \
--cc=wwc@rentec.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