From: Nicolin Chen <nicoleotsuka@gmail.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linux-ia64@vger.kernel.org,
James.Bottomley@HansenPartnership.com, paulus@samba.org,
hpa@zytor.com, sparclinux@vger.kernel.org, hch@lst.de,
sfr@canb.auug.org.au, deller@gmx.de, x86@kernel.org,
borntraeger@de.ibm.com, mingo@redhat.com, mattst88@gmail.com,
fenghua.yu@intel.com, gor@linux.ibm.com, schnelle@linux.ibm.com,
hca@linux.ibm.com, ink@jurassic.park.msu.ru, tglx@linutronix.de,
gerald.schaefer@linux.ibm.com, rth@twiddle.net,
tony.luck@intel.com, linux-parisc@vger.kernel.org,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-alpha@vger.kernel.org, bp@alien8.de,
linuxppc-dev@lists.ozlabs.org, davem@davemloft.net
Subject: Re: [RESEND][PATCH 1/7] powerpc/iommu: Avoid overflow at boundary_size
Date: Tue, 1 Sep 2020 13:53:47 -0700 [thread overview]
Message-ID: <20200901205346.GA17362@Asurada-Nvidia> (raw)
In-Reply-To: <87lfht1vav.fsf@mpe.ellerman.id.au>
On Tue, Sep 01, 2020 at 11:27:36PM +1000, Michael Ellerman wrote:
> Nicolin Chen <nicoleotsuka@gmail.com> writes:
> > The boundary_size might be as large as ULONG_MAX, which means
> > that a device has no specific boundary limit. So either "+ 1"
> > or passing it to ALIGN() would potentially overflow.
> >
> > According to kernel defines:
> > #define ALIGN_MASK(x, mask) (((x) + (mask)) & ~(mask))
> > #define ALIGN(x, a) ALIGN_MASK(x, (typeof(x))(a) - 1)
> >
> > We can simplify the logic here:
> > ALIGN(boundary + 1, 1 << shift) >> shift
> > = ALIGN_MASK(b + 1, (1 << s) - 1) >> s
> > = {[b + 1 + (1 << s) - 1] & ~[(1 << s) - 1]} >> s
> > = [b + 1 + (1 << s) - 1] >> s
> > = [b + (1 << s)] >> s
> > = (b >> s) + 1
> >
> > So fixing a potential overflow with the safer shortcut.
> >
> > Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
> > Signed-off-by: Nicolin Chen <nicoleotsuka@gmail.com>
> > Cc: Christoph Hellwig <hch@lst.de>
> > ---
> > arch/powerpc/kernel/iommu.c | 11 +++++------
> > 1 file changed, 5 insertions(+), 6 deletions(-)
>
> Are you asking for acks, or for maintainers to merge the patches
> individually?
I was expecting that but Christoph just suggested me to squash them
into one so he would merge it: https://lkml.org/lkml/2020/9/1/159
Though I feel it'd be nice to get maintainers' acks before merging.
> > diff --git a/arch/powerpc/kernel/iommu.c b/arch/powerpc/kernel/iommu.c
> > index 9704f3f76e63..c01ccbf8afdd 100644
> > --- a/arch/powerpc/kernel/iommu.c
> > +++ b/arch/powerpc/kernel/iommu.c
> > @@ -236,15 +236,14 @@ static unsigned long iommu_range_alloc(struct device *dev,
> > }
> > }
> >
> > - if (dev)
> > - boundary_size = ALIGN(dma_get_seg_boundary(dev) + 1,
> > - 1 << tbl->it_page_shift);
> > - else
> > - boundary_size = ALIGN(1UL << 32, 1 << tbl->it_page_shift);
> > /* 4GB boundary for iseries_hv_alloc and iseries_hv_map */
> > + boundary_size = dev ? dma_get_seg_boundary(dev) : U32_MAX;
>
> Is there any path that passes a NULL dev anymore?
>
> Both iseries_hv_alloc() and iseries_hv_map() were removed years ago.
> See:
> 8ee3e0d69623 ("powerpc: Remove the main legacy iSerie platform code")
>
>
> So maybe we should do a lead-up patch that drops the NULL dev support,
> which will then make this patch simpler.
The next version of this change will follow Christoph's suggestion
by having a helper function that takes care of !dev internally.
Thanks
Nic
>
>
> > + /* Overflow-free shortcut for: ALIGN(b + 1, 1 << s) >> s */
> > + boundary_size = (boundary_size >> tbl->it_page_shift) + 1;
> >
> > n = iommu_area_alloc(tbl->it_map, limit, start, npages, tbl->it_offset,
> > - boundary_size >> tbl->it_page_shift, align_mask);
> > + boundary_size, align_mask);
> > if (n == -1) {
> > if (likely(pass == 0)) {
> > /* First try the pool from the start */
> > --
> > 2.17.1
next prev parent reply other threads:[~2020-09-01 20:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-31 20:38 [RESEND][PATCH 0/7] Avoid overflow at boundary_size Nicolin Chen
2020-08-31 20:38 ` [RESEND][PATCH 1/7] powerpc/iommu: " Nicolin Chen
2020-09-01 13:27 ` Michael Ellerman
2020-09-01 20:53 ` Nicolin Chen [this message]
2020-08-31 20:38 ` [RESEND][PATCH 2/7] alpha: " Nicolin Chen
2020-08-31 20:38 ` [RESEND][PATCH 3/7] ia64/sba_iommu: " Nicolin Chen
2020-08-31 20:38 ` [RESEND][PATCH 4/7] s390/pci_dma: " Nicolin Chen
2020-08-31 20:38 ` [RESEND][PATCH 5/7] sparc: " Nicolin Chen
2020-08-31 20:38 ` [RESEND][PATCH 6/7] x86/amd_gart: " Nicolin Chen
2020-08-31 20:38 ` [RESEND][PATCH 7/7] parisc: " Nicolin Chen
2020-09-01 7:36 ` [RESEND][PATCH 0/7] " Christoph Hellwig
2020-09-01 7:54 ` Nicolin Chen
2020-09-01 9:11 ` Christoph Hellwig
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=20200901205346.GA17362@Asurada-Nvidia \
--to=nicoleotsuka@gmail.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=borntraeger@de.ibm.com \
--cc=bp@alien8.de \
--cc=davem@davemloft.net \
--cc=deller@gmx.de \
--cc=fenghua.yu@intel.com \
--cc=gerald.schaefer@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=hch@lst.de \
--cc=hpa@zytor.com \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mattst88@gmail.com \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=rth@twiddle.net \
--cc=schnelle@linux.ibm.com \
--cc=sfr@canb.auug.org.au \
--cc=sparclinux@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).