From: mika.westerberg@iki.fi (Mika Westerberg)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND] ARM: fix spinlock recursion in adjust_pte()
Date: Fri, 22 Oct 2010 09:38:45 +0300 [thread overview]
Message-ID: <20101022063845.GI4772@gw.healthdatacare.com> (raw)
In-Reply-To: <20101022062825.GH6225@tarshish>
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)
Regards,
MW
next prev parent reply other threads:[~2010-10-22 6:38 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 [this message]
2010-10-22 6:42 ` Baruch Siach
2010-10-22 7:08 ` Mika Westerberg
2010-10-22 8:01 ` Baruch Siach
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=20101022063845.GI4772@gw.healthdatacare.com \
--to=mika.westerberg@iki.fi \
--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