public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Manfred Spraul <manfred@colorfullife.com>
To: Felipe W Damasio <felipewd@terra.com.br>
Cc: linux-kernel@vger.kernel.org, rnp@netlink.co.nz
Subject: Re: [PATCH] Fix SMP support on 3c527 net driver
Date: Sun, 31 Aug 2003 10:28:19 +0200	[thread overview]
Message-ID: <3F51B1A3.4080307@colorfullife.com> (raw)

Felipe wrote:

>Also, the down/up function doesn't seem to be 
>used in interrupt context, so I think it will work.
>  
>
[snip]

> static int mc32_send_packet(struct sk_buff *skb, struct net_device *dev)
> {
> 	struct mc32_local *lp = (struct mc32_local *)dev->priv;
>-	unsigned long flags;
> 
> 	volatile struct skb_header *p, *np;
> 
> 	netif_stop_queue(dev);
> 
>-	save_flags(flags);
>-	cli();
>+	down(&lp->mc32_sem);
>  
>
No, that's wrong. mc32_send_packet is the hard_start_xmit function, 
called from bottom half context, with the dev_xmit_lock spinlock held.
Additionally, you must replace the sleep_on calls with wait_event, or an 
open-coded wait queue: sleep_on is racy, it only works with cli().

IMHO the right way to fix cli() is
- add a single spinlock to the driver or the device structure. Do not 
forget the spin_lock_init().
- replace cli/sti with spin_lock_irqsave/spin_unlock_irqsave.
- Additionally acquire the spinlock in every interrupt handler (cli() 
stops all interrupts, spinlocks only stop interrupt on the current cpu).
- check if there were recursive cli() calls. Fix them.
- replace all sleep_on calls with wait queue calls.
- check if there are any kmalloc or schedule calls in the area now under 
the spinlock, and reorganize the code.

And please add a changelog entry that code was converted without testing.

--
    Manfred


             reply	other threads:[~2003-08-31  8:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-31  8:28 Manfred Spraul [this message]
2003-08-31 16:50 ` [PATCH] Fix SMP support on 3c527 net driver Felipe W Damasio
2003-08-31 17:30   ` Manfred Spraul
  -- strict thread matches above, loose matches on Subject: below --
2003-08-31  3:06 Felipe W Damasio

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=3F51B1A3.4080307@colorfullife.com \
    --to=manfred@colorfullife.com \
    --cc=felipewd@terra.com.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rnp@netlink.co.nz \
    /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