From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olaf Hering Subject: Re: Re: [PATCH 2 of 4] xentrace: replace ASSERT with printk in __trace_var Date: Mon, 18 Jul 2011 11:04:16 +0200 Message-ID: <20110718090416.GA23376@aepfle.de> References: <1310747494.448.95.camel@elijah> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: George Dunlap , "xen-devel@lists.xensource.com" , George Dunlap List-Id: xen-devel@lists.xenproject.org On Sat, Jul 16, Keir Fraser wrote: > It's not like we have dodgy third-party drivers to worry about. Just fix the > code -- *which is in the tree!* -- that is making the bad calls! It was > correct to make this an assert/bug_on in the first place. trace_irq_mask() was the only function I found with a too large buffer. Olaf