From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Damian Eppel <d.eppel@samsung.com>,
tglx@linutronix.de, kgene@kernel.org, k.kozlowski@samsung.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org
Cc: m.szyprowski@samsung.com, kyungmin.park@samsung.com,
m.jabrzyk@samsung.com, stable@vger.kernel.org
Subject: Re: [RESEND PATCH v3] clocksource: exynos_mct: fix for sleeping in atomic ctx handling cpu hotplug notif.
Date: Mon, 29 Jun 2015 11:19:34 +0200 [thread overview]
Message-ID: <55910DA6.4070404@linaro.org> (raw)
In-Reply-To: <1435324984-7328-1-git-send-email-d.eppel@samsung.com>
On 06/26/2015 03:23 PM, Damian Eppel wrote:
> This is to fix an issue of sleeping in atomic context when processing
> hotplug notifications in Exynos MCT(Multi-Core Timer).
> The issue was reproducible on Exynos 3250 (Rinato board) and Exynos 5420
> (Arndale Octa board).
>
> Whilst testing cpu hotplug events on kernel configured with DEBUG_PREEMPT
> and DEBUG_ATOMIC_SLEEP we get following BUG message, caused by calling
> request_irq() and free_irq() in the context of hotplug notification
> (which is in this case atomic context).
Applied as a 4.2 fix.
Should it be tagged stable@ ?
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
WARNING: multiple messages have this Message-ID (diff)
From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH v3] clocksource: exynos_mct: fix for sleeping in atomic ctx handling cpu hotplug notif.
Date: Mon, 29 Jun 2015 11:19:34 +0200 [thread overview]
Message-ID: <55910DA6.4070404@linaro.org> (raw)
In-Reply-To: <1435324984-7328-1-git-send-email-d.eppel@samsung.com>
On 06/26/2015 03:23 PM, Damian Eppel wrote:
> This is to fix an issue of sleeping in atomic context when processing
> hotplug notifications in Exynos MCT(Multi-Core Timer).
> The issue was reproducible on Exynos 3250 (Rinato board) and Exynos 5420
> (Arndale Octa board).
>
> Whilst testing cpu hotplug events on kernel configured with DEBUG_PREEMPT
> and DEBUG_ATOMIC_SLEEP we get following BUG message, caused by calling
> request_irq() and free_irq() in the context of hotplug notification
> (which is in this case atomic context).
Applied as a 4.2 fix.
Should it be tagged stable@ ?
--
<http://www.linaro.org/> Linaro.org ? Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2015-06-29 9:19 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 9:11 [PATCH v2] clocksource: exynos_mct: fix for sleeping in atomic ctx handling cpu hotplug notif Damian Eppel
2015-03-12 9:11 ` Damian Eppel
2015-05-11 1:33 ` Krzysztof Kozlowski
2015-05-11 1:33 ` Krzysztof Kozlowski
2015-05-11 7:30 ` Daniel Lezcano
2015-05-11 7:30 ` Daniel Lezcano
2015-05-11 11:18 ` Daniel Lezcano
2015-05-11 11:18 ` Daniel Lezcano
2015-05-25 15:24 ` Damian Eppel
2015-05-25 15:24 ` Damian Eppel
2015-05-27 12:43 ` Daniel Lezcano
2015-05-27 12:43 ` Daniel Lezcano
2015-05-28 9:47 ` Marek Szyprowski
2015-05-28 9:47 ` Marek Szyprowski
2015-05-28 15:37 ` Damian Eppel
2015-05-28 15:37 ` Damian Eppel
2015-06-02 11:11 ` [PATCH v3] " Damian Eppel
2015-06-02 11:11 ` Damian Eppel
2015-06-26 13:23 ` [RESEND PATCH " Damian Eppel
2015-06-26 13:23 ` Damian Eppel
2015-06-26 19:54 ` [tip:timers/urgent] clocksource: exynos_mct: Avoid blocking calls in the cpu hotplug notifier tip-bot for Damian Eppel
2015-06-29 9:19 ` Daniel Lezcano [this message]
2015-06-29 9:19 ` [RESEND PATCH v3] clocksource: exynos_mct: fix for sleeping in atomic ctx handling cpu hotplug notif Daniel Lezcano
2015-06-29 9:24 ` Thomas Gleixner
2015-06-29 9:24 ` Thomas Gleixner
2015-06-29 10:14 ` Daniel Lezcano
2015-06-29 10:14 ` Daniel Lezcano
2015-06-29 11:50 ` Krzysztof Kozlowski
2015-06-29 11:50 ` Krzysztof Kozlowski
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=55910DA6.4070404@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=d.eppel@samsung.com \
--cc=k.kozlowski@samsung.com \
--cc=kgene@kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.jabrzyk@samsung.com \
--cc=m.szyprowski@samsung.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.