From mboxrd@z Thu Jan  1 00:00:00 1970
From: Olaf Hering <olaf@aepfle.de>
Subject: how to prevent crashes in notify_via_xen_event_channel
 during shutdown/crash
Date: Tue, 7 Sep 2010 21:52:07 +0200
Message-ID: <20100907195207.GA1428@aepfle.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org


Hello,

I'm seeing crashes with 4.0.1 in notify_via_xen_event_channel() after
evtchn_destroy() was already executed, the ASSERT triggers.
There are a few calls to notify_via_xen_event_channel(), only
hvm_send_assist_req() seems to check the domain->is_shutting_down flag.
xen-unstable is not much different in that area.

How should a check for an already destroyed eventchannel look like?
Maybe like its done in free_xen_event_channel()?

Olaf