From mboxrd@z Thu Jan 1 00:00:00 1970 From: Muli Ben-Yehuda Subject: Re: [PATCH] xencons missing string allocation Date: Fri, 09 Dec 2005 20:54:48 +0200 Message-ID: <20051209185448.GD9830@granada.merseine.nu> References: <1134153451.6136.14.camel@tdi> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7BIT Return-path: In-reply-to: <1134153451.6136.14.camel@tdi> Content-disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Alex Williamson Cc: xen-devel List-Id: xen-devel@lists.xenproject.org On Fri, Dec 09, 2005 at 11:37:31AM -0700, Alex Williamson wrote: > > I was trying to boot dom0 w/ "xencons=ttyS1 console=ttyS1". It gives > some weird error messages: > > Warning: dev (ttyS2) tty->count(2) != #fd's(1) in release_dev > Warning: dev (ttyS2) tty->count(3) != #fd's(1) in tty_open > > And blows up with a page fault. The page fault is because we don't > actually allocate a buffer for the tty driver name. Errr... the patch looks curious. Why does it work when ->name points to the heap but not when it points to the data segment? they should be equivalent and many tty drivers appear to set ->name to the data segment. Is something trying to modify xencons_driver->name later? (also, do you know why do we need the fugly DRV() macro in that code?) Cheers, Muli -- Muli Ben-Yehuda http://www.mulix.org | http://mulix.livejournal.com/