All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Tony Battersby <tonyb@cybernetics.com>
Cc: matthew@wil.cx, linux-scsi@vger.kernel.org,
	James.Bottomley@HansenPartnership.com, protasnb@gmail.com,
	bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bug 3680] sym53c8xx_2 SMP deadlock on driver load
Date: Wed, 17 Oct 2007 17:20:19 +0200	[thread overview]
Message-ID: <20071017152019.GA1871@1wt.eu> (raw)
In-Reply-To: <471621D2.5080806@cybernetics.com>

On Wed, Oct 17, 2007 at 10:53:06AM -0400, Tony Battersby wrote:
> > So we should unconditionally drop the lock (and re-enable
> > interrupts) and re-acquire it.
> 
> After looking at it carefully, this is true of pci_map_mem, but not
> pci_unmap_mem.  pci_unmap_mem can be called from both ->detect and
> ->release.  io_request_lock is held in ->detect but not in ->release.
> So, your patch locks up the system on module unload.
> 
> I have put together and tested a new patch which does it correctly,
> while still trying to make only minimal changes.
> If you approve, this can go into the next 2.4.x release.

(...)

> -static void __init pci_unmap_mem(u_long vaddr, u_long size)
> -{
> -	if (vaddr)
> +static void __init pci_unmap_mem(u_long vaddr,
> +                                 u_long size,
> +                                 int holding_io_request_lock)

This is marked __init, and pci_unmap_mem() is called from
sym_free_resources(), which in turn is called from sym_detach(),
called from sym53c8xx_release() when unloading module. So the section
may not be there anymore upon unload. I wonder how this can work right
now. I'm surely missing something :-/

Willy


  reply	other threads:[~2007-10-17 15:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20071017013045.A19ED108036@picon.linux-foundation.org>
2007-10-17 14:53 ` [Bug 3680] sym53c8xx_2 SMP deadlock on driver load Tony Battersby
2007-10-17 15:20   ` Willy Tarreau [this message]
2007-10-17 15:44     ` Tony Battersby
2007-10-17 15:52       ` Willy Tarreau
2007-10-17 16:22         ` Tony Battersby
2007-10-17 16:27   ` Matthew Wilcox
2007-10-17 18:46     ` Willy Tarreau
2007-10-17 20:12       ` Matthew Wilcox

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=20071017152019.GA1871@1wt.eu \
    --to=w@1wt.eu \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=protasnb@gmail.com \
    --cc=tonyb@cybernetics.com \
    /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.