From: Anna-Maria Gleixner <anna-maria@linutronix.de>
To: linux-kernel@vger.kernel.org
Cc: David Vrabel <david.vrabel@citrix.com>,
xen-devel@lists.xenproject.org,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Anna-Maria Gleixner <anna-maria@linutronix.de>,
rt@linutronix.de
Subject: [PATCH] xen/events/fifo: Add missing hotplug notifier transition
Date: Fri, 11 Mar 2016 10:00:22 +0100 [thread overview]
Message-ID: <1457686822-39117-1-git-send-email-anna-maria__18095.3121897348$1457689783$gmane$org@linutronix.de> (raw)
The evtchn_fifo_cpu_notification() hotplug callback lacks handling of
the CPU_UP_CANCELED case. That means, if CPU_UP_PREPARE fails, the
handle of the fifo events is not dropped.
Add handling for CPU_UP_CANCELED transition to drop the fifo events
handle.
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: David Vrabel <david.vrabel@citrix.com>
Cc: xen-devel@lists.xenproject.org
Signed-off-by: Anna-Maria Gleixner <anna-maria@linutronix.de>
---
drivers/xen/events/events_fifo.c | 1 +
1 file changed, 1 insertion(+)
--- a/drivers/xen/events/events_fifo.c
+++ b/drivers/xen/events/events_fifo.c
@@ -432,6 +432,7 @@ static int evtchn_fifo_cpu_notification(
ret = evtchn_fifo_alloc_control_block(cpu);
break;
case CPU_DEAD:
+ case CPU_UP_CANCELED:
__evtchn_fifo_handle_events(cpu, true);
break;
default:
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next reply other threads:[~2016-03-11 9:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 9:00 Anna-Maria Gleixner [this message]
[not found] <1457686822-39117-1-git-send-email-anna-maria@linutronix.de>
2016-03-11 10:53 ` [PATCH] xen/events/fifo: Add missing hotplug notifier transition David Vrabel
[not found] ` <56E2A3B6.2060208@citrix.com>
2016-03-11 11:26 ` Anna-Maria Gleixner
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='1457686822-39117-1-git-send-email-anna-maria__18095.3121897348$1457689783$gmane$org@linutronix.de' \
--to=anna-maria@linutronix.de \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rt@linutronix.de \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).