From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: chenwy <chenwy-fnst@cn.fujitsu.com>
Cc: <linux-mtd@lists.infradead.org>,
fnstml-fjl@cn.fujitsu.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtd: mtdram: check offs and len in mtdram->point madram->unpoint, mtdram->write and mtdram->read
Date: Thu, 16 Mar 2017 10:20:49 +0100 [thread overview]
Message-ID: <20170316102049.4bcc2b7d@bbrezillon> (raw)
In-Reply-To: <20170303073100.27590-1-chenwy-fnst@cn.fujitsu.com>
Hi Chen,
Can you use something shorter for your commit title. Something like
"mtd: mtdram: check offs and len where appropriate"
On Fri, 3 Mar 2017 15:31:00 +0800
chenwy <chenwy-fnst@cn.fujitsu.com> wrote:
> We should prevent user to erasing mtd device with
^ from
> an unaligned offset or length.
Why are you putting 5 spaces before each line of your commit message?
>
> Signed-off-by: Chen Wenyong <chenwy-fnst@cn.fujitsu.com>
> ---
> drivers/mtd/devices/mtdram.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/drivers/mtd/devices/mtdram.c b/drivers/mtd/devices/mtdram.c
> index cbd8547..b0468c1 100644
> --- a/drivers/mtd/devices/mtdram.c
> +++ b/drivers/mtd/devices/mtdram.c
> @@ -67,6 +67,8 @@ static int ram_erase(struct mtd_info *mtd, struct erase_info *instr)
> static int ram_point(struct mtd_info *mtd, loff_t from, size_t len,
> size_t *retlen, void **virt, resource_size_t *phys)
> {
> + if (check_offs_len(mtd, from, len))
> + return -EINVAL;
Add an empty line.
> *virt = mtd->priv + from;
> *retlen = len;
> return 0;
> @@ -74,6 +76,8 @@ static int ram_point(struct mtd_info *mtd, loff_t from, size_t len,
>
> static int ram_unpoint(struct mtd_info *mtd, loff_t from, size_t len)
> {
> + if (check_offs_len(mtd, from, len))
> + return -EINVAL;
Ditto.
> return 0;
> }
>
> @@ -93,6 +97,8 @@ static unsigned long ram_get_unmapped_area(struct mtd_info *mtd,
> static int ram_read(struct mtd_info *mtd, loff_t from, size_t len,
> size_t *retlen, u_char *buf)
> {
> + if (check_offs_len(mtd, from, len))
> + return -EINVAL;
Ditto.
> memcpy(buf, mtd->priv + from, len);
> *retlen = len;
> return 0;
> @@ -101,6 +107,8 @@ static int ram_read(struct mtd_info *mtd, loff_t from, size_t len,
> static int ram_write(struct mtd_info *mtd, loff_t to, size_t len,
> size_t *retlen, const u_char *buf)
> {
> + if (check_offs_len(mtd, to, len))
> + return -EINVAL;
Ditto.
> memcpy((char *)mtd->priv + to, buf, len);
> *retlen = len;
> return 0;
prev parent reply other threads:[~2017-03-16 9:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 7:31 [PATCH] mtd: mtdram: check offs and len in mtdram->point madram->unpoint, mtdram->write and mtdram->read chenwy
2017-03-16 9:20 ` Boris Brezillon [this message]
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=20170316102049.4bcc2b7d@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=chenwy-fnst@cn.fujitsu.com \
--cc=fnstml-fjl@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.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