mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Colin Ian King <colin.king@canonical.com>
To: David Woodhouse <dwmw2@infradead.org>,
	Brian Norris <computersforpeace@gmail.com>,
	Boris Brezillon <boris.brezillon@free-electrons.com>,
	Marek Vasut <marek.vasut@gmail.com>,
	Richard Weinberger <richard@nod.at>,
	Cyrille Pitchen <cyrille.pitchen@wedev4u.fr>,
	Andrea Adami <andrea.adami@gmail.com>,
	linux-mtd@lists.infradead.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: NAK: [PATCH][mtd-next] mtd: sharpslpart: fix overflow on block_adr calculation
Date: Wed, 8 Nov 2017 15:57:57 +0000	[thread overview]
Message-ID: <c69cae0f-0490-20b7-9706-78d2ef2d3c73@canonical.com> (raw)
In-Reply-To: <20171108154649.30096-1-colin.king@canonical.com>

On 08/11/17 15:46, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
> 
> Multiplying block_num and mtd->erasesize may potentially overflow
> as they are both unsigned ints and so the multiplication is evaluated
> in unsigned int arithmetic .  Cast block_adr to off_t to ensure
> multiplication is off_t sized to avoid any potential overflow.
> 
> Detected by CoverityScan, CID#1461264 ("Unintentional integer overflow")
> 
> Fixes: fff1e32a50c0 ("mtd: sharpslpart: Add sharpslpart partition parser")
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
>  drivers/mtd/parsers/sharpslpart.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/mtd/parsers/sharpslpart.c b/drivers/mtd/parsers/sharpslpart.c
> index 5fe0079ea5ed..b1d97aa3bac4 100644
> --- a/drivers/mtd/parsers/sharpslpart.c
> +++ b/drivers/mtd/parsers/sharpslpart.c
> @@ -244,7 +244,7 @@ static int sharpsl_nand_read_laddr(struct mtd_info *mtd,
>  		return -EINVAL;
>  
>  	block_num = ftl->log2phy[log_num];
> -	block_adr = block_num * mtd->erasesize;
> +	block_adr = (loff_t)block_num * mtd->erasesize;
>  	block_ofs = mtd_mod_by_eb((u32)from, mtd);
>  
>  	err = mtd_read(mtd, block_adr + block_ofs, len, &retlen, buf);
> 

Sorry, ignore this, there is another place that does this that needs
some attention. I'll sent V2 shortly.

  reply	other threads:[~2017-11-08 15:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-08 15:46 Colin King
2017-11-08 15:57 ` Colin Ian King [this message]
2017-11-08 16:01   ` NAK: " Richard Weinberger

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=c69cae0f-0490-20b7-9706-78d2ef2d3c73@canonical.com \
    --to=colin.king@canonical.com \
    --cc=andrea.adami@gmail.com \
    --cc=boris.brezillon@free-electrons.com \
    --cc=computersforpeace@gmail.com \
    --cc=cyrille.pitchen@wedev4u.fr \
    --cc=dwmw2@infradead.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=marek.vasut@gmail.com \
    --cc=richard@nod.at \
    /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®