From: Mark Brown <broonie@kernel.org>
To: Stefan Wahren <stefan.wahren@i2se.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Joe Perches <joe@perches.com>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH V2] regulator: core: fix constraints debug output
Date: Tue, 9 Jun 2015 19:00:28 +0100 [thread overview]
Message-ID: <20150609180028.GT14071@sirena.org.uk> (raw)
In-Reply-To: <1433368589-16806-1-git-send-email-stefan.wahren@i2se.com>
[-- Attachment #1: Type: text/plain, Size: 398 bytes --]
On Wed, Jun 03, 2015 at 09:56:29PM +0000, Stefan Wahren wrote:
> The line buffer for constraints debug isn't big enough to hold the output
> in all cases. So fix the possible buffer overflow by the usage of the
> scnprintf().
If we know how much output we might produce then why not extend the
buffer so we don't need to cut it off? The defensive programming is
good but that seems a better fix.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-06-09 18:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 21:56 Stefan Wahren
2015-06-09 18:00 ` Mark Brown [this message]
2015-06-09 18:49 ` Stefan Wahren
2015-06-09 18:57 ` Mark Brown
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=20150609180028.GT14071@sirena.org.uk \
--to=broonie@kernel.org \
--cc=joe@perches.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=stefan.wahren@i2se.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
all inboxes | Powered by JetHome®