linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Smart <James.Smart@Emulex.Com>
To: Tore Anderson <tore@linpro.no>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-scsi@vger.kernel.org, James Smart <James.Smart@Emulex.Com>
Subject: Re: Linux 2.6.23-rc3
Date: Tue, 14 Aug 2007 08:25:59 -0400	[thread overview]
Message-ID: <46C19F57.3070801@emulex.com> (raw)
In-Reply-To: <46C1717E.3030908@linpro.no>

fyi....

I've seen these before (and they haven't been specific to the LLDD).

The "-EEXIST" error, was an issue of rescan-while-deleting, and where
refcounts held the old sdevs in place. They were ramant in 2.6.18/2.6.19.
Supposedly, we had patches from Hannes Reinecke. to resolve it, but that
was a while ago.  Additionally, the traps around the attribute containers
are similar. There are still some cases of data structures being freed
(and thus erroneously reused later) in the midlayer and transports
even though the refcounts on child-structures haven't finished.

If you believe these are related to the -rc3 lpfc mods, I recommend
retesting on an -rc2 or 2.6.22 to see how similar they are.

I'll pull in -rc3 and see if I can't see more on my end..

-- james s

Tore Anderson wrote:
>   I gave it a spin, and got quite a few troubles that appears related to
>  the lpfc driver.  I don't know if these problems happened due to the
>  recent update as the latest kernel I ran before was 2.6.20 (where I
>  never saw problems like these).  First I see that something failed when
>  the volumes on the SAN (on a Sun StorageTek 6140 / Engenio 3994) is
>  registered, causing two errors errors such as:

  parent reply	other threads:[~2007-08-14 12:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-13  4:50 Linux 2.6.23-rc3 Linus Torvalds
2007-08-13  6:25 ` Michal Piotrowski
2007-08-13 12:23 ` Zilvinas Valinskas
2007-08-13 16:49   ` Michal Piotrowski
2007-08-14 10:14     ` Zilvinas Valinskas
2007-08-14 10:10   ` Zilvinas Valinskas
2007-08-14  9:10 ` Tore Anderson
2007-08-14 11:24   ` Matthew Wilcox
2007-08-14 13:04     ` James Smart
     [not found]       ` <1187186897.1457.57.camel@potomac.tworiverlabs.com>
2007-08-15 14:47         ` Matthew Wilcox
2007-08-14 18:31     ` Tore Anderson
2007-08-15 12:59       ` Tore Anderson
2007-08-14 12:25   ` James Smart [this message]
2007-08-14 13:07     ` Tore Anderson

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=46C19F57.3070801@emulex.com \
    --to=james.smart@emulex.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=tore@linpro.no \
    --cc=torvalds@linux-foundation.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 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).