From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Alan D. Brunelle" <Alan.Brunelle@hp.com>
Cc: Andrew Vasquez <andrew.vasquez@qlogic.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jens Axboe <jens.axboe@oracle.com>,
linux-driver@qlogic.com, linux-scsi@vger.kernel.org
Subject: Re: Issue with qla2xxx_probe_one
Date: Tue, 29 Apr 2008 19:39:54 -0500 [thread overview]
Message-ID: <1209515994.4448.25.camel@localhost.localdomain> (raw)
In-Reply-To: <48178143.2000308@hp.com>
On Tue, 2008-04-29 at 16:12 -0400, Alan D. Brunelle wrote:
> Andrew Vasquez wrote:
> > On Tue, 29 Apr 2008, Alan D. Brunelle wrote:
> >
> >> I /think/ that there is an issue with this routine /if/ the firmware
> >> images are not loaded properly - on a 16-way ia64 box I am starting to
> >> see this with an up-stream kernel (Jens Axboe's origin/io-cpu-affinity
> >> branch). In any event, it looks to me that :
> >>
> >> if (qla2x00_initialize_adapter(ha)) {
> >> qla_printk(KERN_WARNING, ha,
> >> "Failed to initialize adapter\n");
> >>
> >> DEBUG2(printk("scsi(%ld): Failed to initialize
> adapter - "
> >> "Adapter flags %x.\n",
> >> ha->host_no, ha->device_flags));
> >>
> >> ret = -ENODEV;
> >> goto probe_failed;
> >> }
> >>
> >> skips around:
> >>
> >> ret = scsi_add_host(host, &pdev->dev);
> >>
> >> which is needed to properly initialize the freelist (via:
> >> scsi_setup_command_freelist).
> >
> > Wasn't something like this posted recently to linux-scsi:
> >
> > http://lkml.org/lkml/2008/4/27/333
> >
> > this is sitting in scsi-misc-2.6.git:
> >
> > [SCSI] bug fix for free list handling
> >
> http://git.kernel.org/?p=linux/kernel/git/jejb/scsi-misc-2.6.git;a=commitdiff;h=a79cbe1aa5dd695f0ee012ecde1ff88b1192e326
> >
> > which I gather will be pushed soon...
>
> My apologies for not having seeing that.
>
> But after looking at it, doesn't it still have a hole?
>
> o scsi_setup_command_freelist initializes the free_list list.
>
> o It then invokes scsi_get_host_cmd_pool, if this fails there is no
> need to invoke scsi_put_host_cmd_pool (it wasn't gotten).
>
> o If scsi_get_host_cmd_pool succeeds but scsi_pool_alloc_command fails,
> it will (correctly) invoke scsi_put_host_cmd_pool.
>
> However, if either of scsi_get_host_cmd_pool or scsi_put_host_cmd_pool
> happens to fail, we'll end up in scsi_destroy_command_freelist - and
> since the free_list was initialized, the while loop will be bypassed,
> but scsi_put_host_cmd_pool will be invoked an extra time. And this is
> badness, right?
>
> Wouldn't the attached patch [boot tested on my previously failing
> system] be correct (and perhaps cleaner - you're not looking at the
> innards of the list data structure to determine things)?
Yes, that looks like a better fix. I tidied up your change log, because
it's helpful to identify the original problem commit, but otherwise
applied it unchanged.
Thanks,
James
prev parent reply other threads:[~2008-04-30 3:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 17:34 Issue with qla2xxx_probe_one Alan D. Brunelle
2008-04-29 17:44 ` Andrew Vasquez
2008-04-29 20:12 ` Alan D. Brunelle
2008-04-29 21:26 ` Andrew Vasquez
2008-04-29 22:57 ` FUJITA Tomonori
2008-04-30 0:39 ` James Bottomley [this message]
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=1209515994.4448.25.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=Alan.Brunelle@hp.com \
--cc=andrew.vasquez@qlogic.com \
--cc=jens.axboe@oracle.com \
--cc=linux-driver@qlogic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.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