public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Michael Schmitz <schmitzmic@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
	Christoph Hellwig <hch@infradead.org>
Cc: linux-block <linux-block@vger.kernel.org>,
	Jens Axboe <axboe@kernel.dk>,
	Linux/m68k <linux-m68k@vger.kernel.org>,
	Greg KH <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v8 2/2] block: add overflow checks for Amiga partition support
Date: Tue, 23 Aug 2022 08:38:32 +1200	[thread overview]
Message-ID: <81e8bd2a-bb3f-6da0-ed39-b522a6b822be@gmail.com> (raw)
In-Reply-To: <CAMuHMdWW1=kXC14H6iUFF61sMOnsbfXodKS=mpdNbCtvgvjqKA@mail.gmail.com>

Hi Geert,

On 11/08/22 23:40, Geert Uytterhoeven wrote:
> Hi Christoph,
>
> On Tue, Jul 26, 2022 at 1:43 PM Christoph Hellwig <hch@infradead.org> wrote:
>> On Tue, Jul 26, 2022 at 04:57:47PM +1200, Michael Schmitz wrote:
>>> The Amiga partition parser module uses signed int for partition sector
>>> address and count, which will overflow for disks larger than 1 TB.
>>>
>>> Use u64 as type for sector address and size to allow using disks up to
>>> 2 TB without LBD support, and disks larger than 2 TB with LBD. The RBD
>>> format allows to specify disk sizes up to 2^128 bytes (though native
>>> OS limitations reduce this somewhat, to max 2^68 bytes), so check for
>>> u64 overflow carefully to protect against overflowing sector_t.
>>>
>>> Bail out if sector addresses overflow 32 bits on kernels without LBD
>>> support.
>>>
>>> This bug was reported originally in 2012, and the fix was created by
>>> the RDB author, Joanne Dow <jdow@earthlink.net>. A patch had been
>>> discussed and reviewed on linux-m68k at that time but never officially
>>> submitted (now resubmitted as separate patch).
>>> This patch adds additional error checking and warning messages.
>>>
>>> Fixes: https://bugzilla.kernel.org/show_bug.cgi?id=43511
>>> Reported-by: Martin Steigerwald <Martin@lichtvoll.de>
>>> Message-ID: <201206192146.09327.Martin@lichtvoll.de>
>>> Signed-off-by: Michael Schmitz <schmitzmic@gmail.com>
>>> Reviewed-by: Geert Uytterhoeven <geert@linux-m68k.org>
>>> --- a/block/partitions/amiga.c
>>> +++ b/block/partitions/amiga.c
>>>                if (!data) {
>>> -                     pr_err("Dev %s: unable to read RDB block %d\n",
>>> -                            state->disk->disk_name, blk);
>>> +                     pr_err("Dev %s: unable to read RDB block %llu\n",
>>> +                            state->disk->disk_name, (u64) blk);
>> No need for the various printk casts, a sector_t is always an
>> unsigned long long.
> That is true, as of commit 72deb455b5ec619f
> ("block: remove CONFIG_LBDAF") in v5.2.
> Since 4.9, 4.14, and 4.19 are still receiving stable updates, the
> cast should be re-added when this is backported.

Does this require a note in the commit message, or explicit CC to Greg?

Cheers,

     Michael

> Gr{oetje,eeting}s,
>
>                          Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
>                                  -- Linus Torvalds

  reply	other threads:[~2022-08-22 20:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-26  4:57 [PATCH v8 0/2] Amiga RDB partition support fixes Michael Schmitz
2022-07-26  4:57 ` [PATCH v8 1/2] block: fix signed int overflow in Amiga partition support Michael Schmitz
2022-07-26 11:41   ` Christoph Hellwig
2022-07-26  4:57 ` [PATCH v8 2/2] block: add overflow checks for " Michael Schmitz
2022-07-26 11:42   ` Christoph Hellwig
2022-07-26 22:28     ` Michael Schmitz
2022-08-11 11:40     ` Geert Uytterhoeven
2022-08-22 20:38       ` Michael Schmitz [this message]
2022-08-22 21:03         ` Geert Uytterhoeven
2022-08-22 21:09           ` Michael Schmitz
2022-07-26 12:53   ` kernel test robot

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=81e8bd2a-bb3f-6da0-ed39-b522a6b822be@gmail.com \
    --to=schmitzmic@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=geert@linux-m68k.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@infradead.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-m68k@vger.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