public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: baruch@tkos.co.il (Baruch Siach)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND] ARM: fix spinlock recursion in adjust_pte()
Date: Fri, 22 Oct 2010 10:01:52 +0200	[thread overview]
Message-ID: <20101022080152.GJ6225@tarshish> (raw)
In-Reply-To: <20101022070847.GJ4772@gw.healthdatacare.com>

Hi Mika,

On Fri, Oct 22, 2010 at 10:08:47AM +0300, Mika Westerberg wrote:
> On Fri, Oct 22, 2010 at 08:42:05AM +0200, Baruch Siach wrote:
> > Hi Mika,
> > 
> > On Fri, Oct 22, 2010 at 09:38:45AM +0300, Mika Westerberg wrote:
> > > On Fri, Oct 22, 2010 at 08:28:26AM +0200, Baruch Siach wrote:
> > > [...]
> > > > 
> > > > Do you have any idea when was this bug introduced? Does it affect already 
> > > > release kernels other than .36?
> > > 
> > > I've seen it at least on .35. The locking code itself was introduced
> > > in commit:
> > > 
> > > 56dd47098abe (ARM: make_coherent: fix problems with highpte, part 1)
> > 
> > Which is present on .34-rc1. In this case adding stable at kernel.org to Cc would 
> > be nice.
> 
> Ok, thanks.
> 
> I'm not familiar with the stable rules and it wasn't immediately
> clear from the Documentation/stable_kernel_rules.txt: should I resend
> this patch with added 'Cc:' or is it enough just to add Cc into followup
> mail?

Patch with 'Cc: stable at kernel.org' line in its commit log is automatically 
forwarded to the stable team once this patch hits Linus' tree. Since this 
patch should go through Russell's tree, you can add this line when posting to 
his patch tracker. I guess that adding some info in the commit log on the 
history of this bug should help the stable team in the process.

baruch

-- 
                                                     ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

      reply	other threads:[~2010-10-22  8:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-21 14:12 BUG: spinlock recursion on CPU#0 Alexander Stein
2010-10-21 16:44 ` Mika Westerberg
2010-10-21 17:09   ` [PATCH RESEND] ARM: fix spinlock recursion in adjust_pte() Mika Westerberg
2010-10-22  6:28     ` Baruch Siach
2010-10-22  6:38       ` Mika Westerberg
2010-10-22  6:42         ` Baruch Siach
2010-10-22  7:08           ` Mika Westerberg
2010-10-22  8:01             ` Baruch Siach [this message]

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=20101022080152.GJ6225@tarshish \
    --to=baruch@tkos.co.il \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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