From: <gregkh@linuxfoundation.org>
To: broonie@kernel.org, gregkh@linuxfoundation.org, linux@rasmusvillemoes.dk
Cc: <stable@vger.kernel.org>, <stable-commits@vger.kernel.org>
Subject: Patch "regmap: debugfs: Don't bother actually printing when calculating max length" has been added to the 4.1-stable tree
Date: Sat, 17 Oct 2015 15:04:34 -0700 [thread overview]
Message-ID: <14451194748313@kroah.com> (raw)
This is a note to let you know that I've just added the patch titled
regmap: debugfs: Don't bother actually printing when calculating max length
to the 4.1-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
regmap-debugfs-don-t-bother-actually-printing-when-calculating-max-length.patch
and it can be found in the queue-4.1 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@vger.kernel.org> know about it.
>From 176fc2d5770a0990eebff903ba680d2edd32e718 Mon Sep 17 00:00:00 2001
From: Mark Brown <broonie@kernel.org>
Date: Sat, 19 Sep 2015 07:12:34 -0700
Subject: regmap: debugfs: Don't bother actually printing when calculating max length
From: Mark Brown <broonie@kernel.org>
commit 176fc2d5770a0990eebff903ba680d2edd32e718 upstream.
The in kernel snprintf() will conveniently return the actual length of
the printed string even if not given an output beffer at all so just do
that rather than relying on the user to pass in a suitable buffer,
ensuring that we don't need to worry if the buffer was truncated due to
the size of the buffer passed in.
Reported-by: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Signed-off-by: Mark Brown <broonie@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
drivers/base/regmap/regmap-debugfs.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
--- a/drivers/base/regmap/regmap-debugfs.c
+++ b/drivers/base/regmap/regmap-debugfs.c
@@ -32,8 +32,7 @@ static DEFINE_MUTEX(regmap_debugfs_early
/* Calculate the length of a fixed format */
static size_t regmap_calc_reg_len(int max_val, char *buf, size_t buf_size)
{
- snprintf(buf, buf_size, "%x", max_val);
- return strlen(buf);
+ return snprintf(NULL, 0, "%x", max_val);
}
static ssize_t regmap_name_read_file(struct file *file,
Patches currently in stable-queue which might be from broonie@kernel.org are
queue-4.1/asoc-pxa-pxa2xx-ac97-fix-dma-requestor-lines.patch
queue-4.1/spi-xtensa-xtfpga-fix-register-endianness.patch
queue-4.1/regmap-debugfs-ensure-we-don-t-underflow-when-printing-access-masks.patch
queue-4.1/spi-fix-documentation-of-spi_alloc_master.patch
queue-4.1/asoc-fix-broken-pxa-soc-support.patch
queue-4.1/asoc-sgtl5000-fix-wrong-register-mic_bias_voltage-setup-on-probe.patch
queue-4.1/asoc-dwc-correct-irq-clear-method.patch
queue-4.1/asoc-db1200-fix-dai-link-format-for-db1300-and-db1550.patch
queue-4.1/spi-spidev-fix-possible-null-dereference.patch
queue-4.1/regmap-debugfs-don-t-bother-actually-printing-when-calculating-max-length.patch
queue-4.1/spi-spi-pxa2xx-check-status-register-to-determine-if-sssr_tint-is-disabled.patch
reply other threads:[~2015-10-17 22:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=14451194748313@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=broonie@kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.