From: Cao jin <caoj.fnst@cn.fujitsu.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: mst@redhat.com, jasowang@redhat.com, qemu-devel@nongnu.org,
dmitry@daynix.com, alex.williamson@redhat.com, hare@suse.de,
marcel@redhat.com, pbonzini@redhat.com, jsnow@redhat.com,
kraxel@redhat.com
Subject: Re: [Qemu-devel] [PATCH v4 3/5] megasas: bugfix
Date: Sat, 9 Apr 2016 21:07:45 +0800 [thread overview]
Message-ID: <5708FEA1.5070802@cn.fujitsu.com> (raw)
In-Reply-To: <87a8l4tvry.fsf@dusky.pond.sub.org>
On 04/08/2016 03:16 PM, Markus Armbruster wrote:
> Please use a more descriptive title. Suggest "megasas: Fix
>
> Cao jin <caoj.fnst@cn.fujitsu.com> writes:
>
>> msi_init returns non-zero value on both failure and success
>
> This is a sentence, should end with a period.
>
> Bug's impact? Here's my guess.
>
> msi_init() either succeeds and returns 0x50, or fails and returns a
> negative errno. If it succeeds, we mistakenly clear
> MEGASAS_MASK_USE_MSI. Its only use is in megasas_scsi_uninit(), via
> megasas_use_msi(). There, we fail to msi_uninit() on unrealize due to
> the bug.
>
> I figure that's harmless if we destroy the device next. This is the
> common case.
>
> If we don't destroy it, and then realize it again, msi_init() fails,
FYI: if realize it again, I guess msi_init() won`t be executed again,
because megasas_use_msi() will fail first.
> because there's no space at 0x50: the MSI capability we neglected to
> delete is still there. We report the problem to the user, then realize
> the device anyway (I hate that, but it's a separate issue).
>
--
Yours Sincerely,
Cao jin
next prev parent reply other threads:[~2016-04-09 13:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 11:26 [Qemu-devel] [PATCH v4 0/5] Add param Error ** for msi_init() Cao jin
2016-04-05 11:26 ` [Qemu-devel] [PATCH v4 1/5] fix some coding style problems Cao jin
2016-04-08 6:29 ` Markus Armbruster
2016-04-09 8:49 ` Cao jin
2016-04-05 11:26 ` [Qemu-devel] [PATCH v4 2/5] change pvscsi_init_msi() type to void Cao jin
2016-04-06 7:19 ` Dmitry Fleytman
2016-04-10 7:41 ` Marcel Apfelbaum
2016-04-05 11:26 ` [Qemu-devel] [PATCH v4 3/5] megasas: bugfix Cao jin
2016-04-08 7:16 ` Markus Armbruster
2016-04-09 13:07 ` Cao jin [this message]
2016-04-10 7:40 ` Marcel Apfelbaum
2016-04-05 11:26 ` [Qemu-devel] [PATCH v4 4/5] mptsas: change .realize function name Cao jin
2016-04-10 7:43 ` Marcel Apfelbaum
2016-04-05 11:26 ` [Qemu-devel] [PATCH v4 5/5] Add param Error ** for msi_init() Cao jin
2016-04-08 8:44 ` Markus Armbruster
2016-04-09 12:19 ` Cao jin
2016-04-09 13:00 ` Cao jin
2016-04-10 8:20 ` Marcel Apfelbaum
2016-04-10 9:38 ` Cao jin
2016-04-11 10:00 ` Marcel Apfelbaum
2016-04-11 12:02 ` Cao jin
2016-04-12 11:50 ` Markus Armbruster
2016-04-29 9:28 ` Cao jin
2016-04-29 12:46 ` Markus Armbruster
2016-04-12 8:34 ` Markus Armbruster
2016-04-05 11:27 ` [Qemu-devel] [PATCH v4 0/5] " Michael S. Tsirkin
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=5708FEA1.5070802@cn.fujitsu.com \
--to=caoj.fnst@cn.fujitsu.com \
--cc=alex.williamson@redhat.com \
--cc=armbru@redhat.com \
--cc=dmitry@daynix.com \
--cc=hare@suse.de \
--cc=jasowang@redhat.com \
--cc=jsnow@redhat.com \
--cc=kraxel@redhat.com \
--cc=marcel@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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).