From: Michael Schmitz <schmitzmic@gmail.com>
To: linux-block@vger.kernel.org, axboe@kernel.dk
Cc: linux-m68k@vger.kernel.org, geert@linux-m68k.org, hch@lst.de,
martin@lichtvoll.de, fthain@linux-m68k.org,
Michael Schmitz <schmitzmic@gmail.com>
Subject: [PATCH v13 0/3] Amiga RDB partition support fixes
Date: Wed, 21 Jun 2023 08:17:22 +1200 [thread overview]
Message-ID: <20230620201725.7020-1-schmitzmic@gmail.com> (raw)
Hi Jens,
another last version of this patch series, only change
in this version is in the patch 2 subject (to better
reflect what it's about), and adding Geert's review
tag to said patch.
I hope I've crossed all i's and dotted all t's now...
Cheers,
Michael
Michael Schmitz (3):
block: fix signed int overflow in Amiga partition support
block: change all __u32 annotations to __be32 in affs_hardblocks.h
block: add overflow checks for Amiga partition support
block/partitions/amiga.c | 102 ++++++++++++++++++++++-----
include/uapi/linux/affs_hardblocks.h | 68 +++++++++---------
2 files changed, 119 insertions(+), 51 deletions(-)
--
2.17.1
next reply other threads:[~2023-06-20 20:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 20:17 Michael Schmitz [this message]
2023-06-20 20:17 ` [PATCH v13 1/3] block: fix signed int overflow in Amiga partition support Michael Schmitz
2023-06-20 20:17 ` [PATCH v13 2/3] block: change all __u32 annotations to __be32 in affs_hardblocks.h Michael Schmitz
2023-06-20 20:17 ` [PATCH v13 3/3] block: add overflow checks for Amiga partition support Michael Schmitz
2023-06-20 20:28 ` [PATCH v13 0/3] Amiga RDB partition support fixes Jens Axboe
2023-06-20 21:16 ` Martin Steigerwald
2023-06-21 5:54 ` John Paul Adrian Glaubitz
2023-06-20 21:17 ` Michael Schmitz
2023-07-04 23:38 ` [PATCH v4 0/1] Bugfix for Amiga partition fixes Michael Schmitz
2023-07-04 23:38 ` [PATCH v4 1/1] block: bugfix for Amiga partition overflow check patch Michael Schmitz
2023-07-05 7:28 ` Geert Uytterhoeven
2023-07-05 8:53 ` Michael Schmitz
2023-07-05 9:08 ` Geert Uytterhoeven
2023-07-05 19:25 ` Michael Schmitz
2023-07-05 20:42 ` Jens Axboe
2023-07-05 21:41 ` Michael Schmitz
2023-07-05 21:44 ` Jens Axboe
2023-07-05 22:09 ` Michael Schmitz
2023-07-05 22:13 ` Jens Axboe
2023-07-05 22:25 ` Michael Schmitz
2023-07-05 22:34 ` Jens Axboe
2023-07-05 22:38 ` Jens Axboe
2023-07-05 23:54 ` Michael Schmitz
2023-07-06 7:23 ` Martin Steigerwald
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=20230620201725.7020-1-schmitzmic@gmail.com \
--to=schmitzmic@gmail.com \
--cc=axboe@kernel.dk \
--cc=fthain@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=martin@lichtvoll.de \
/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