From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: "Thomas Petazzoni" <thomas.petazzoni@free-electrons.com>,
"Noralf Trønnes" <noralf@tronnes.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: fbtft: fix out of bound access
Date: Thu, 4 Jun 2015 17:51:53 +0530 [thread overview]
Message-ID: <20150604122153.GA18177@sudip-PC> (raw)
In-Reply-To: <1433419943.4861.167.camel@perches.com>
On Thu, Jun 04, 2015 at 05:12:23AM -0700, Joe Perches wrote:
> On Thu, 2015-06-04 at 17:12 +0530, Sudip Mukherjee wrote:
> > size of str is 16, but in snprintf the size was mentioned as 128.
> []
> > diff --git a/drivers/staging/fbtft/fbtft-core.c b/drivers/staging/fbtft/fbtft-core.c
> []
> > @@ -1096,7 +1096,7 @@ static int fbtft_init_display_dt(struct fbtft_par *par)
> > /* make debug message */
> > msg[0] = '\0';
> > for (j = 0; j < i; j++) {
> > - snprintf(str, 128, " %02X", buf[j]);
> > + snprintf(str, 16, " %02X", buf[j]);
>
> using sizeof(str) is probably more robust
>
> msg isn't big enough to hold the maximum possible output.
yes, it will not hold. i didn't notice msg size.
>
> If this is really useful, and I rather doubt it is,
> it'd probably be better to use a loop to output
> multiple lines, one for each register.
I will send in a v2 doing this.
regards
sudip
>
>
next prev parent reply other threads:[~2015-06-04 12:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-04 11:42 [PATCH] staging: fbtft: fix out of bound access Sudip Mukherjee
2015-06-04 12:12 ` Joe Perches
2015-06-04 12:21 ` Sudip Mukherjee [this message]
2015-06-04 12:36 ` Dan Carpenter
2015-06-04 12:47 ` Sudip Mukherjee
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=20150604122153.GA18177@sudip-PC \
--to=sudipm.mukherjee@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=noralf@tronnes.org \
--cc=thomas.petazzoni@free-electrons.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