From: Greg KH <greg@kroah.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Felipe Contreras <felipe.contreras@nokia.com>,
linux-main <linux-kernel@vger.kernel.org>,
linux-omap <linux-omap@vger.kernel.org>,
Omar Ramirez Luna <omar.ramirez@ti.com>,
Ohad Ben-Cohen <ohad@wizery.com>,
Fernando Guzman Lugo <fernando.lugo@ti.com>,
Nishanth Menon <nm@ti.com>,
Ameya Palande <ameya.palande@nokia.com>
Subject: Re: [PATCH] staging: tidspbridge: protect dmm_map properly
Date: Mon, 7 Mar 2011 10:48:00 -0800 [thread overview]
Message-ID: <20110307184800.GA13355@kroah.com> (raw)
In-Reply-To: <AANLkTi=w=5L8tbjGDCgoRpjRXYrNxsfWaE2SL4XG9+pY@mail.gmail.com>
On Mon, Mar 07, 2011 at 08:02:44PM +0200, Felipe Contreras wrote:
> On Mon, Dec 20, 2010 at 7:12 PM, Felipe Contreras
> <felipe.contreras@nokia.com> wrote:
> > We need to protect not only the dmm_map list, but the individual
> > map_obj's, otherwise, we might be building the scatter-gather list with
> > garbage. So, use the existing proc_lock for that.
> >
> > I observed race conditions which caused kernel panics while running
> > stress tests. This patch fixes those.
>
> I just heard that Tuomas Kulve is getting a lot of panics on Gumstix
> Overo. I propose we apply this patch on the stable tree ASAP, and if
> there's no better proposals, also on .38.
Um, I don't think you realize _how_ stable trees work, please go read
Documentation/stable_kernel_rules.txt to see how it is not possible to
take something into the stable releases before it goes to Linus's tree.
Sorry,
greg k-h
next prev parent reply other threads:[~2011-03-07 18:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 17:12 [PATCH] staging: tidspbridge: protect dmm_map properly Felipe Contreras
2010-12-20 18:30 ` Kanigeri, Hari
2010-12-20 18:43 ` Felipe Contreras
2011-03-07 18:02 ` Felipe Contreras
2011-03-07 18:14 ` Ohad Ben-Cohen
2011-03-07 18:48 ` Greg KH [this message]
2011-03-07 19:29 ` Ramirez Luna, Omar
2011-03-07 21:48 ` Felipe Contreras
-- strict thread matches above, loose matches on Subject: below --
2011-03-12 0:29 Omar Ramirez Luna
2011-03-12 17:36 ` Greg KH
2011-03-12 23:42 ` Felipe Contreras
2011-03-13 1:06 ` Greg KH
2011-03-14 15:33 ` Felipe Contreras
2011-03-14 15:53 ` Greg KH
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=20110307184800.GA13355@kroah.com \
--to=greg@kroah.com \
--cc=ameya.palande@nokia.com \
--cc=felipe.contreras@gmail.com \
--cc=felipe.contreras@nokia.com \
--cc=fernando.lugo@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=ohad@wizery.com \
--cc=omar.ramirez@ti.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