public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Michał Kępień" <kernel@kempniu.pl>
To: Miquel Raynal <miquel.raynal@bootlin.com>,
	Richard Weinberger <richard@nod.at>,
	Vignesh Raghavendra <vigneshr@ti.com>
Cc: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] mtdchar_write_ioctl(): prevent integer overflow, use kvmalloc()
Date: Mon, 16 May 2022 09:05:59 +0200	[thread overview]
Message-ID: <20220516070601.11428-1-kernel@kempniu.pl> (raw)

This patch series addresses two flaws in mtdchar_write_ioctl() found by
Richard Weinberger while he was reviewing v3 of the patch series
proposing a new MEMREAD ioctl [1].

Richard, I included a Suggested-by tag crediting you in both of the
patches in this series.  I hope that is okay with you, but please let me
know if it isn't.

Once this patch series is reviewed and accepted, I will apply similar
fixes in v4 of the MEMREAD ioctl patch series.

[1] https://lists.infradead.org/pipermail/linux-mtd/2022-February/091276.html

Michał Kępień (2):
  mtdchar: prevent integer overflow in a safety check
  mtdchar: use kvmalloc() for potentially large allocations

 drivers/mtd/mtdchar.c      | 13 ++++++++-----
 include/uapi/mtd/mtd-abi.h |  4 ++--
 2 files changed, 10 insertions(+), 7 deletions(-)

-- 
2.36.1



______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

             reply	other threads:[~2022-05-16  7:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-16  7:05 Michał Kępień [this message]
2022-05-16  7:06 ` [PATCH 1/2] mtdchar: prevent integer overflow in a safety check Michał Kępień
2022-06-07 20:23   ` Richard Weinberger
2022-06-09 13:10   ` Miquel Raynal
2022-05-16  7:06 ` [PATCH 2/2] mtdchar: use kvmalloc() for potentially large allocations Michał Kępień
2022-06-07 20:30   ` Richard Weinberger
2022-06-09 13:10   ` Miquel Raynal

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=20220516070601.11428-1-kernel@kempniu.pl \
    --to=kernel@kempniu.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=richard@nod.at \
    --cc=vigneshr@ti.com \
    /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