linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: mike.tummy@gmail.com, linux-scsi@vger.kernel.org,
	bugzilla-daemon@bugzilla.kernel.org, Greg KH <greg@kroah.com>
Subject: Re: [Bug 13311] New: mptsas: ioc0: removing ssp device, kernel oops
Date: Thu, 28 May 2009 13:54:05 +0200	[thread overview]
Message-ID: <ac3eb2510905280454p1cdcbf0cxbb8e2907209ae974@mail.gmail.com> (raw)
In-Reply-To: <20090528010038.b4d3b2b9.akpm@linux-foundation.org>

On Thu, May 28, 2009 at 10:00, Andrew Morton <akpm@linux-foundation.org> wrote:

>>            Product: SCSI Drivers
>>            Version: 2.5
>>     Kernel Version: 2.6.27.21
>
> Is it reproducible?  If so, is there any change that it can be retested
> under a 2.6.29-based kernel?

This driver version:
  MPT_LINUX_VERSION_COMMON       "4.00.43.00suse"
seems not in the upstream kernel:
  MPT_LINUX_VERSION_COMMON       "3.04.07"

The failing code is only in the new driver. This bug should move to
the Novell bugzilla, so the people who added the driver to the SUSE
kernel can check with LSI directly.

> OK, I assume that the scsi driver did something bad to sysfs and
> that sysfs then fell on its face.
>
> Really, given the frequency and imaginativeness with which drivers
> abuse sysfs, the driver-core should be more robust.
>
> Kay, would you have time to plunk through this and see if we can
> strengthen the sysfs code a bit so it doesn't crash?

Might be a missing lock/wrong refcounting issue in the caller, where
two threads try to remove the same thing. With Eric's upcoming changes
to the cleanup logic in sysfs, this should be handled better.

Thanks,
Kay
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-05-28 11:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-14 18:17 [Bug 13311] New: mptsas: ioc0: removing ssp device, kernel oops bugzilla-daemon
2009-05-28  8:00 ` Andrew Morton
2009-05-28 11:54   ` Kay Sievers [this message]
2009-06-09 21:27   ` Mike Loseke
2009-06-09 21:52     ` Andrew Morton
2009-05-28  8:01 ` [Bug 13311] " bugzilla-daemon
2009-05-28 11:54 ` bugzilla-daemon
2009-06-09 21:27 ` bugzilla-daemon
2009-06-09 21:30 ` bugzilla-daemon
2009-06-09 21:53 ` bugzilla-daemon
2009-07-16 21:41 ` bugzilla-daemon

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=ac3eb2510905280454p1cdcbf0cxbb8e2907209ae974@mail.gmail.com \
    --to=kay.sievers@vrfy.org \
    --cc=akpm@linux-foundation.org \
    --cc=bugzilla-daemon@bugzilla.kernel.org \
    --cc=greg@kroah.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mike.tummy@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).