All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernard Pidoux <pidoux@ccr.jussieu.fr>
To: Ralf Baechle DL5RB <ralf@linux-mips.org>
Cc: linux-hams@vger.kernel.org
Subject: Re: ROSE lockup fix
Date: Thu, 09 Feb 2006 17:25:12 +0100	[thread overview]
Message-ID: <43EB6CE8.8030302@ccr.jussieu.fr> (raw)
In-Reply-To: <20060118083816.GA7510@linux-mips.org>

Hi Ralf,

I applied your rose patch to the more recent kernel 2.6.15.2 and it 
seems to work fine as there are no more spinlock recursion related to 
rose when killall during reboot process.

However I observed a new problem only once.

Here is the screen dump copied from a digital photo
(I did not copy the <numbers> but only symbolic names) :

Sending all processes the TERM signal...
BUG: spinlock bad magic on CPU#0, ax25ipd/4703
  lock: ea6b4318, .magic: 00000000, .owner: <none>/-1, .owner_cpu:0
dump_stack
spin_bug
_raw_spin_lock
_spin_lock_irqsave
__wake_up
sock_def_write_space
sock_wfree
__kfree_skb
skb_queue_purge
ax25_clear_queues   [ax25]
ax25_disconnect     [ax25]
ax25_kill_by_device [ax25]
ax25_device_event   [ax25]
notifier_call_chain
dev_close
unregister_netdevice
unregister_netdev
mkiss_close         [mkiss]
release_dev
tty_release
__fput
fput
filp_close
put_files_struct
do_exit
do_group_exit
sys_exit_group
sysenter_past_esp

---------------------------

Ralf Baechle DL5RB wrote :
> On Wed, Jan 18, 2006 at 01:08:43AM +0000, Ralf Baechle DL5RB wrote:
> 
> 
>>Anyway, the problem is pretty obvious in your traceback and I'll cook a
>>patch for you to test.
> 
> 
> Can you test the patch below?
> 
>   Ralf
> 
>  net/rose/rose_route.c |    7 -------
>  1 files changed, 7 deletions(-)
> 
> Index: linux-mips/net/rose/rose_route.c
> ===================================================================
> --- linux-mips.orig/net/rose/rose_route.c
> +++ linux-mips/net/rose/rose_route.c
> @@ -48,8 +48,6 @@ static DEFINE_SPINLOCK(rose_route_list_l
>  
>  struct rose_neigh *rose_loopback_neigh;
>  
> -static void rose_remove_neigh(struct rose_neigh *);
> -
>  /*
>   *	Add a new route to a node, and in the process add the node and the
>   *	neighbour if it is new.
> @@ -235,11 +233,8 @@ static void rose_remove_neigh(struct ros
>  
>  	skb_queue_purge(&rose_neigh->queue);
>  
> -	spin_lock_bh(&rose_neigh_list_lock);
> -
>  	if ((s = rose_neigh_list) == rose_neigh) {
>  		rose_neigh_list = rose_neigh->next;
> -		spin_unlock_bh(&rose_neigh_list_lock);
>  		kfree(rose_neigh->digipeat);
>  		kfree(rose_neigh);
>  		return;
> @@ -248,7 +243,6 @@ static void rose_remove_neigh(struct ros
>  	while (s != NULL && s->next != NULL) {
>  		if (s->next == rose_neigh) {
>  			s->next = rose_neigh->next;
> -			spin_unlock_bh(&rose_neigh_list_lock);
>  			kfree(rose_neigh->digipeat);
>  			kfree(rose_neigh);
>  			return;
> @@ -256,7 +250,6 @@ static void rose_remove_neigh(struct ros
>  
>  		s = s->next;
>  	}
> -	spin_unlock_bh(&rose_neigh_list_lock);
>  }
>  
>  /*
> -
> To unsubscribe from this list: send the line "unsubscribe linux-hams" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 

-- 

73 de Bernard, f6bvp

http://f6bvp.free.fr
http://f6bvp.org (mirror)
http://rose.fpac.free.fr/

  parent reply	other threads:[~2006-02-09 16:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-11 17:45 AX25 patches and how it affects the end user Douglas Cole
2006-01-11 22:14 ` Mike McCarthy, W1NR
2006-01-12  0:55   ` Douglas Cole
2006-01-13 21:09   ` Ralf Baechle DL5RB
2006-01-17 16:59     ` Bernard Pidoux
2006-01-18  1:08       ` Ralf Baechle DL5RB
2006-01-18  8:38         ` ROSE lockup fix Ralf Baechle DL5RB
2006-01-19 16:44           ` Bernard Pidoux
2006-02-09 16:25           ` Bernard Pidoux [this message]
2006-01-18 12:26         ` AX25 patches and how it affects the end user Chuck Hast
2006-01-18 21:52           ` Ralf Baechle DL5RB

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=43EB6CE8.8030302@ccr.jussieu.fr \
    --to=pidoux@ccr.jussieu.fr \
    --cc=linux-hams@vger.kernel.org \
    --cc=ralf@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.