From: Logan Gunthorpe <logang@deltatee.com>
To: Bjorn Helgaas <helgaas@kernel.org>,
Wesley Sheng <wesley.sheng@microchip.com>
Cc: kurt.schwemmer@microsemi.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, wesleyshenggit@sina.com
Subject: Re: [PATCH v2 1/2] switchtec: Fix false maximum supported PCIe function number issue
Date: Thu, 18 Apr 2019 09:49:56 -0600 [thread overview]
Message-ID: <b3318670-f7f4-5f2e-751a-e028d4caf0b9@deltatee.com> (raw)
In-Reply-To: <20190417224858.GW126710@google.com>
On 2019-04-17 4:48 p.m., Bjorn Helgaas wrote:
>> ---
>> drivers/pci/switch/switchtec.c | 39 +++++++++++++++++++++++++-----------
>> include/linux/switchtec.h | 2 +-
>> include/uapi/linux/switchtec_ioctl.h | 13 +++++++++++-
>> 3 files changed, 40 insertions(+), 14 deletions(-)
>>
>> diff --git a/drivers/pci/switch/switchtec.c b/drivers/pci/switch/switchtec.c
>> index e22766c..7df9a69 100644
>> --- a/drivers/pci/switch/switchtec.c
>> +++ b/drivers/pci/switch/switchtec.c
>> @@ -658,19 +658,25 @@ static int ioctl_flash_part_info(struct switchtec_dev *stdev,
>>
>> static int ioctl_event_summary(struct switchtec_dev *stdev,
>> struct switchtec_user *stuser,
>> - struct switchtec_ioctl_event_summary __user *usum)
>> + struct switchtec_ioctl_event_summary __user *usum,
>> + size_t size)
>> {
>> - struct switchtec_ioctl_event_summary s = {0};
>> + struct switchtec_ioctl_event_summary *s;
>> int i;
>> u32 reg;
>> + int ret = 0;
>>
>> - s.global = ioread32(&stdev->mmio_sw_event->global_summary);
>> - s.part_bitmap = ioread32(&stdev->mmio_sw_event->part_event_bitmap);
>> - s.local_part = ioread32(&stdev->mmio_part_cfg->part_event_summary);
>> + s = kzalloc(sizeof(*s), GFP_KERNEL);
>> + if (!s)
>> + return -ENOMEM;
>> +
>> + s->global = ioread32(&stdev->mmio_sw_event->global_summary);
>> + s->part_bitmap = ioread32(&stdev->mmio_sw_event->part_event_bitmap);
>> + s->local_part = ioread32(&stdev->mmio_part_cfg->part_event_summary);
>>
>> for (i = 0; i < stdev->partition_count; i++) {
>> reg = ioread32(&stdev->mmio_part_cfg_all[i].part_event_summary);
>> - s.part[i] = reg;
>> + s->part[i] = reg;
>> }
>>
>> for (i = 0; i < SWITCHTEC_MAX_PFF_CSR; i++) {
>
> Should this be "i < stdev->pff_csr_count", as in
> check_link_state_events(), enable_link_state_events() and
> mask_all_events()? If so, I assume the read and check of vendor_id
> would be unnecessary?
Yes, nice catch. I think that would be a good simplification.
> The last loop in init_pff() currently checks against
> SWITCHTEC_MAX_PFF_CSR:
>
> for (i = 0; i < ARRAY_SIZE(pcfg->dsp_pff_inst_id); i++) {
> reg = ioread32(&pcfg->dsp_pff_inst_id[i]);
> if (reg < SWITCHTEC_MAX_PFF_CSR)
> stdev->pff_local[reg] = 1;
> }
>
> Should it check "reg < stdev->pff_csr_count" instead? It looks like
> mask_all_events(), the only reader of pff_local[], only looks up to
> pff_csr_count anyway.
Yeah, I could go either way. The hardware would have to be broken if reg
was between pff_csr_count and SWITCHTEC_MAX_PFF_CSR. This is mostly to
catch 0xFF which indicates it's unset (if I recall correctly).
Logan
next prev parent reply other threads:[~2019-04-18 15:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-15 14:41 [PATCH v2 0/2] Fix two bugs of switchtec module Wesley Sheng
2019-04-15 14:41 ` [PATCH v2 1/2] switchtec: Fix false maximum supported PCIe function number issue Wesley Sheng
2019-04-17 22:48 ` Bjorn Helgaas
[not found] ` <20190418165621.GA5272@sina.com>
2019-04-18 13:09 ` Bjorn Helgaas
2019-04-18 15:49 ` Logan Gunthorpe [this message]
2019-04-15 14:41 ` [PATCH v2 2/2] switchtec: Fix unintended mask of MRPC event Wesley Sheng
2019-04-18 13:49 ` Bjorn Helgaas
2019-04-15 15:51 ` [PATCH v2 0/2] Fix two bugs of switchtec module Logan Gunthorpe
2019-04-18 13:55 ` Bjorn Helgaas
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=b3318670-f7f4-5f2e-751a-e028d4caf0b9@deltatee.com \
--to=logang@deltatee.com \
--cc=helgaas@kernel.org \
--cc=kurt.schwemmer@microsemi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=wesley.sheng@microchip.com \
--cc=wesleyshenggit@sina.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
all inboxes | Powered by JetHome®