From: Michael Ellerman <mpe@ellerman.id.au>
To: Nicolin Chen <nicoleotsuka@gmail.com>,
benh@kernel.crashing.org, paulus@samba.org, rth@twiddle.net,
ink@jurassic.park.msu.ru, mattst88@gmail.com,
tony.luck@intel.com, fenghua.yu@intel.com,
schnelle@linux.ibm.com, gerald.schaefer@linux.ibm.com,
hca@linux.ibm.com, gor@linux.ibm.com, borntraeger@de.ibm.com,
davem@davemloft.net, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, x86@kernel.org, hpa@zytor.com,
James.Bottomley@HansenPartnership.com, deller@gmx.de
Cc: sfr@canb.auug.org.au, linux-ia64@vger.kernel.org,
linux-parisc@vger.kernel.org, linux-s390@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-alpha@vger.kernel.org,
sparclinux@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
hch@lst.de
Subject: Re: [RESEND][PATCH 1/7] powerpc/iommu: Avoid overflow at boundary_size
Date: Tue, 01 Sep 2020 23:27:36 +1000 [thread overview]
Message-ID: <87lfht1vav.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <20200831203811.8494-2-nicoleotsuka@gmail.com>
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?
> 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.
cheers
> + /* 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
WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <mpe@ellerman.id.au>
To: Nicolin Chen <nicoleotsuka@gmail.com>,
benh@kernel.crashing.org, paulus@samba.org, rth@twiddle.net,
ink@jurassic.park.msu.ru, mattst88@gmail.com,
tony.luck@intel.com, fenghua.yu@intel.com,
schnelle@linux.ibm.com, gerald.schaefer@linux.ibm.com,
hca@linux.ibm.com, gor@linux.ibm.com, borntraeger@de.ibm.com,
davem@davemloft.net, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, x86@kernel.org, hpa@zytor.com,
James.Bottomley@HansenPartnership.com, deller@gmx.de
Cc: sfr@canb.auug.org.au, hch@lst.de, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org, linux-alpha@vger.kernel.org,
linux-ia64@vger.kernel.org, linux-s390@vger.kernel.org,
sparclinux@vger.kernel.org, linux-parisc@vger.kernel.org
Subject: Re: [RESEND][PATCH 1/7] powerpc/iommu: Avoid overflow at boundary_size
Date: Tue, 01 Sep 2020 13:27:36 +0000 [thread overview]
Message-ID: <87lfht1vav.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <20200831203811.8494-2-nicoleotsuka@gmail.com>
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?
> 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.
cheers
> + /* 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
WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <mpe@ellerman.id.au>
To: Nicolin Chen <nicoleotsuka@gmail.com>,
benh@kernel.crashing.org, paulus@samba.org, rth@twiddle.net,
ink@jurassic.park.msu.ru, mattst88@gmail.com,
tony.luck@intel.com, fenghua.yu@intel.com,
schnelle@linux.ibm.com, gerald.schaefer@linux.ibm.com,
hca@linux.ibm.com, gor@linux.ibm.com, borntraeger@de.ibm.com,
davem@davemloft.net, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, x86@kernel.org, hpa@zytor.com,
James.Bottomley@HansenPartnership.com, deller@gmx.de
Cc: sfr@canb.auug.org.au, hch@lst.de, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org, linux-alpha@vger.kernel.org,
linux-ia64@vger.kernel.org, linux-s390@vger.kernel.org,
sparclinux@vger.kernel.org, linux-parisc@vger.kernel.org
Subject: Re: [RESEND][PATCH 1/7] powerpc/iommu: Avoid overflow at boundary_size
Date: Tue, 01 Sep 2020 23:27:36 +1000 [thread overview]
Message-ID: <87lfht1vav.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <20200831203811.8494-2-nicoleotsuka@gmail.com>
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?
> 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.
cheers
> + /* 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 13:27 UTC|newest]
Thread overview: 39+ 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 ` Nicolin Chen
2020-08-31 20:38 ` Nicolin Chen
2020-08-31 20:38 ` [RESEND][PATCH 1/7] powerpc/iommu: " Nicolin Chen
2020-08-31 20:38 ` Nicolin Chen
2020-08-31 20:38 ` Nicolin Chen
2020-09-01 13:27 ` Michael Ellerman [this message]
2020-09-01 13:27 ` Michael Ellerman
2020-09-01 13:27 ` Michael Ellerman
2020-09-01 20:53 ` Nicolin Chen
2020-09-01 20:53 ` Nicolin Chen
2020-09-01 20:53 ` Nicolin Chen
2020-08-31 20:38 ` [RESEND][PATCH 2/7] alpha: " Nicolin Chen
2020-08-31 20:38 ` Nicolin Chen
2020-08-31 20:38 ` Nicolin Chen
2020-08-31 20:38 ` [RESEND][PATCH 3/7] ia64/sba_iommu: " Nicolin Chen
2020-08-31 20:38 ` Nicolin Chen
2020-08-31 20:38 ` Nicolin Chen
2020-08-31 20:38 ` [RESEND][PATCH 4/7] s390/pci_dma: " Nicolin Chen
2020-08-31 20:38 ` Nicolin Chen
2020-08-31 20:38 ` Nicolin Chen
2020-08-31 20:38 ` [RESEND][PATCH 5/7] sparc: " Nicolin Chen
2020-08-31 20:38 ` Nicolin Chen
2020-08-31 20:38 ` Nicolin Chen
2020-08-31 20:38 ` [RESEND][PATCH 6/7] x86/amd_gart: " Nicolin Chen
2020-08-31 20:38 ` Nicolin Chen
2020-08-31 20:38 ` Nicolin Chen
2020-08-31 20:38 ` [RESEND][PATCH 7/7] parisc: " Nicolin Chen
2020-08-31 20:38 ` Nicolin Chen
2020-08-31 20:38 ` Nicolin Chen
2020-09-01 7:36 ` [RESEND][PATCH 0/7] " Christoph Hellwig
2020-09-01 7:36 ` Christoph Hellwig
2020-09-01 7:36 ` Christoph Hellwig
2020-09-01 7:54 ` Nicolin Chen
2020-09-01 7:54 ` Nicolin Chen
2020-09-01 7:54 ` Nicolin Chen
2020-09-01 9:11 ` Christoph Hellwig
2020-09-01 9:11 ` Christoph Hellwig
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=87lfht1vav.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=James.Bottomley@HansenPartnership.com \
--cc=benh@kernel.crashing.org \
--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=nicoleotsuka@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.