public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst•de>
To: Nicolin Chen <nicoleotsuka@gmail•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
	Christoph Hellwig <hch@lst•de>,
	Linux Next Mailing List <linux-next@vger•kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: boot failure after merge of the dma-mapping tree
Date: Thu, 20 Aug 2020 17:49:41 +0200	[thread overview]
Message-ID: <20200820154941.GA11349@lst.de> (raw)
In-Reply-To: <20200820083617.GA6124@Asurada>

On Thu, Aug 20, 2020 at 01:36:17AM -0700, Nicolin Chen wrote:
> Took a quick look -- the boundary_size is seemingly passed from
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/arch/powerpc/kernel/iommu.c#n240
> 
> 	boundary_size = ALIGN(dma_get_seg_boundary(dev) + 1,
> 			1 << tbl->it_page_shift);
> 
> Looks like an overflow happens due to (ULONG_MAX + 1). Should
> we fix here instead (or also)?

Yes, please.  I'll drop the patch again for now, but once we've
got this sorted out I'll readd it.

  reply	other threads:[~2020-08-20 15:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-20  5:51 linux-next: boot failure after merge of the dma-mapping tree Stephen Rothwell
2020-08-20  8:36 ` Nicolin Chen
2020-08-20 15:49   ` Christoph Hellwig [this message]
2020-08-20 20:31     ` Nicolin Chen
  -- strict thread matches above, loose matches on Subject: below --
2025-07-09 13:39 Stephen Rothwell
2025-07-09 17:41 ` Leon Romanovsky
2025-07-09 23:46   ` Stephen Rothwell
2025-07-09 18:16 ` Leon Romanovsky
2025-07-10  0:10   ` Stephen Rothwell

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=20200820154941.GA11349@lst.de \
    --to=hch@lst$(echo .)de \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=nicoleotsuka@gmail$(echo .)com \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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