From: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
To: Jike Song <albcamus@gmail.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
jbarnes@virtuousgeek.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] PCI/MSI: bugfix/utilize for msi_capability_init()
Date: Thu, 25 Dec 2008 15:17:54 +0900 [thread overview]
Message-ID: <49532592.9050202@jp.fujitsu.com> (raw)
In-Reply-To: <df9815e70812240101q23f6d59fj4121b19563a77d47@mail.gmail.com>
Jike Song wrote:
> On Wed, Dec 24, 2008 at 4:27 PM, Hidetoshi Seto
> <seto.hidetoshi@jp.fujitsu.com> wrote:
>> This patch fix a following bug and does a cleanup.
>>
>> bug:
>> commit 5993760f7fc75b77e4701f1e56dc84c0d6cf18d5
>> had a wrong change (since is_64 is boolean[0|1]):
>>
>> - pci_write_config_dword(dev,
>> - msi_mask_bits_reg(pos, is_64bit_address(control)),
>> - maskbits);
>> + pci_write_config_dword(dev, entry->msi_attrib.is_64, maskbits);
>>
> Yes, really a nasty bug. I'm feeling guilty...
> Should this fix hit 2.6.28 release? I CCed Jesse for his point.
Unfortunately we failed to take this fix into Santa's bag...
Note that this bug affects mask condition after calling pci_enable_msi()
for devices with MSI capability with (optional) per-vector masking support.
Devices with MSI-X or MSI without masking support are safe.
Once unmask/mask_msi_irq() is called, the condition should be fixed.
And the wrong pci_write_config_dword() will have no effects because
target registers (fields in header, such as Vendor ID) are read-only.
Thanks,
H.Seto
next prev parent reply other threads:[~2008-12-25 6:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-24 8:27 [PATCH] PCI/MSI: bugfix/utilize for msi_capability_init() Hidetoshi Seto
2008-12-24 9:01 ` Jike Song
2008-12-25 6:17 ` Hidetoshi Seto [this message]
2009-01-16 18:32 ` Jesse Barnes
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=49532592.9050202@jp.fujitsu.com \
--to=seto.hidetoshi@jp.fujitsu.com \
--cc=albcamus@gmail.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--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