From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: David Laight <David.Laight@ACULAB.COM>
Cc: 'Niklas Cassel' <niklas.cassel@axis.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Niklas Cassel <niklass@axis.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 3/3] PCI: endpoint: Fix find_first_zero_bit() usage
Date: Tue, 28 Nov 2017 12:13:12 +0000 [thread overview]
Message-ID: <20171128121312.GA15106@red-moon> (raw)
In-Reply-To: <227791f09ccd4aa8972ba334fd948f4e@AcuMS.aculab.com>
On Tue, Nov 28, 2017 at 09:53:12AM +0000, David Laight wrote:
> From: Niklas Cassel
> > Sent: 27 November 2017 15:50
> > find_first_zero_bit()'s parameter 'size' is defined in bits,
> > not in bytes.
> >
> > Calling find_first_zero_bit() with the wrong size unit
> > will lead to insidious bugs.
> >
> > Fix this by calling find_first_zero_bit() with size
> > BITS_PER_LONG, rather than sizeof().
> >
> > Also add proper error handling for find_first_zero_bit(),
> > since this was missing.
> >
> > Fixes: d74679911610 ("PCI: endpoint: Introduce configfs entry for configuring EP functions")
> > Signed-off-by: Niklas Cassel <niklas.cassel@axis.com>
> > ---
> > drivers/pci/endpoint/pci-ep-cfs.c | 8 +++++++-
> > 1 file changed, 7 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/pci/endpoint/pci-ep-cfs.c b/drivers/pci/endpoint/pci-ep-cfs.c
> > index e1f5adc9e113..0a22a7976580 100644
> > --- a/drivers/pci/endpoint/pci-ep-cfs.c
> > +++ b/drivers/pci/endpoint/pci-ep-cfs.c
> > @@ -109,7 +109,12 @@ static int pci_epc_epf_link(struct config_item *epc_item,
> > return ret;
> >
> > func_no = find_first_zero_bit(&epc_group->function_num_map,
> > - sizeof(epc_group->function_num_map));
> > + BITS_PER_LONG);
>
> Surely this should be either 8 * sizeof() or you should use ffz()
> that takes a numeric argument rather than the function designed
> for arbitrary size bitmaps.
Do you see a problem with this code ? It can be made a bitmap by
allocating it using epc->max_functions as bitmap number of bits
and that can be made on top of the code above that would go in
as a fix unless you strongly object to it, as Joe mentioned
both ffz+| and find_first_zero_bit()+set_bit() are ok with me as
long as we choose one and fix the issue.
Thanks,
Lorenzo
prev parent reply other threads:[~2017-11-28 12:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 15:49 [PATCH v3 0/3] Fix find_first_zero_bit() usage Niklas Cassel
2017-11-27 15:49 ` [PATCH v3 1/3] PCI: designware-ep: " Niklas Cassel
2017-11-27 16:55 ` Lorenzo Pieralisi
2017-12-08 11:21 ` Lorenzo Pieralisi
2017-11-27 15:49 ` [PATCH v3 2/3] PCI: endpoint: Fix error handling in pci_epc_epf_link() Niklas Cassel
2017-11-27 16:16 ` Lorenzo Pieralisi
2017-11-27 15:49 ` [PATCH v3 3/3] PCI: endpoint: Fix find_first_zero_bit() usage Niklas Cassel
2017-11-27 17:44 ` Lorenzo Pieralisi
2017-11-28 9:53 ` David Laight
2017-11-28 12:13 ` Lorenzo Pieralisi [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=20171128121312.GA15106@red-moon \
--to=lorenzo.pieralisi@arm.com \
--cc=David.Laight@ACULAB.COM \
--cc=bhelgaas@google.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=niklas.cassel@axis.com \
--cc=niklass@axis.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;
as well as URLs for NNTP newsgroup(s).