linux-um archives
 help / color / mirror / Atom feed
From: Bodo Stroesser <bstroesser@fujitsu-siemens.com>
To: Jeff Dike <jdike@addtoit.com>
Cc: Blaisorblade <blaisorblade_spam@yahoo.it>,
	user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Patchset to implement PTRACE_SYSEMU_SINGLESTEP
Date: Thu, 18 Nov 2004 15:19:45 +0100	[thread overview]
Message-ID: <419CAF81.9010408@fujitsu-siemens.com> (raw)
In-Reply-To: <200411180647.iAI6lSQ3008451@ccure.user-mode-linux.org>

Jeff Dike wrote:
> bstroesser@fujitsu-siemens.com said:
> 
>>What happens on my system shows some other symptoms. After "Restarting
>>system." UML exits without further message. I could track this down to
>>a SIGIO being unblocked immediately before the execvp(). It is handled
>>by sig_handler() that calls sig_handler_common_skas(). Why this exits,
>>I don't know. 
> 
> 
> Try this patch.  It adds the missing closes that you found today, plus it
> makes sure that netdevices get closed down correctly.
> 
> 				Jeff

Yes. I've tested and mostly it works fine. Only one litte change is needed
to have the daemon-network working after "network stop" and "network start".
I commented it in the patch.

         Bodo

> 
> Index: 2.6.9/arch/um/drivers/net_kern.c
> ===================================================================
> --- 2.6.9.orig/arch/um/drivers/net_kern.c	2004-11-17 22:25:19.000000000 -0500
> +++ 2.6.9/arch/um/drivers/net_kern.c	2004-11-17 23:18:21.000000000 -0500
> @@ -126,10 +126,6 @@
>  	lp->tl.data = (unsigned long) &lp->user;
>  	netif_start_queue(dev);
>  
> -	spin_lock(&opened_lock);
> -	list_add(&lp->list, &opened);
> -	spin_unlock(&opened_lock);
> -
>  	/* clear buffer - it can happen that the host side of the interface
>  	 * is full when we get here.  In this case, new data is never queued,
>  	 * SIGIOs never arrive, and the net never works.
> @@ -150,11 +146,10 @@
>  
>  	free_irq_by_irq_and_dev(dev->irq, dev);
A little question: what about the "free_irq_by_irq_and_dev"? In my sources they
are missing, and I couldn't find a patch relating this. My daemon works without it.
>  	free_irq(dev->irq, dev);


> -	if(lp->close != NULL) (*lp->close)(lp->fd, &lp->user);
> -	lp->fd = -1;
These two lines should be unchanged. lp->fd must be set to -1, since net_kern
for all networks takes this as a "is-closed" flag and refuses to open,
if lp->fd != -1. Daemon stores its fds in a private struct and returns it in
case of an open(). Thus, lp->fd is set to daemon's fd on each open().


> -	spin_lock(&opened_lock);
> -	list_del(&lp->list);
> -	spin_unlock(&opened_lock);
Yes. This must be removed.


> +	if(lp->close != NULL){
> +		(*lp->close)(lp->fd, &lp->user);
> +		lp->fd = -1;
> +	}
No. This must not be inserted.


>  
>  	spin_unlock(&lp->lock);
>  	return 0;
> @@ -289,7 +284,7 @@
>  static spinlock_t devices_lock = SPIN_LOCK_UNLOCKED;
>  static struct list_head devices = LIST_HEAD_INIT(devices);
>  
> -static int eth_configure(int n, void *init, char *mac,
> +static int eth_configure(int n, void *init, char *mac, 
>  			 struct transport *transport)
>  {
>  	struct uml_net *device;
> @@ -397,6 +392,11 @@
>  
>  	if (device->have_mac)
>  		set_ether_mac(dev, device->mac);
> +
> +	spin_lock(&opened_lock);
> +	list_add(&lp->list, &opened);
> +	spin_unlock(&opened_lock);
> +
>  	return(0);
>  }
>  
> @@ -705,7 +705,7 @@
>  static void close_devices(void)
>  {
>  	struct list_head *ele;
> -	struct uml_net_private *lp;	
> +	struct uml_net_private *lp;
>  
>  	list_for_each(ele, &opened){
>  		lp = list_entry(ele, struct uml_net_private, list);
> Index: 2.6.9/arch/um/kernel/initrd_user.c
> ===================================================================
> --- 2.6.9.orig/arch/um/kernel/initrd_user.c	2004-11-17 22:25:19.000000000 -0500
> +++ 2.6.9/arch/um/kernel/initrd_user.c	2004-11-17 22:26:24.000000000 -0500
> @@ -29,6 +29,8 @@
>  		       filename, -n);
>  		return(-1);
>  	}
> +
> +	os_close_file(fd);
>  	return(0);
>  }
>  
> Index: 2.6.9/arch/um/kernel/mem_user.c
> ===================================================================
> --- 2.6.9.orig/arch/um/kernel/mem_user.c	2004-11-17 22:25:19.000000000 -0500
> +++ 2.6.9/arch/um/kernel/mem_user.c	2004-11-17 22:26:24.000000000 -0500
> @@ -101,6 +101,8 @@
>  	}
>  	printf("OK\n");
>  	munmap(addr, UM_KERN_PAGE_SIZE);
> +
> +	os_close_file(fd);
>  }
>  
>  static int have_devanon = 0;
> 



-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  reply	other threads:[~2004-11-18 14:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-12 20:05 [uml-devel] Patchset to implement PTRACE_SYSEMU_SINGLESTEP Bodo Stroesser
2004-11-12 23:43 ` Blaisorblade
2004-11-15 17:11   ` Bodo Stroesser
2004-11-18  6:47     ` Jeff Dike
2004-11-18 14:19       ` Bodo Stroesser [this message]
2004-11-18 14:41         ` Blaisorblade
2004-11-18 16:01           ` Bodo Stroesser
2004-12-06 20:33 ` Blaisorblade
2004-12-07 14:21   ` Bodo Stroesser

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=419CAF81.9010408@fujitsu-siemens.com \
    --to=bstroesser@fujitsu-siemens.com \
    --cc=blaisorblade_spam@yahoo.it \
    --cc=jdike@addtoit.com \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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