public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: Maurizio Lombardi <mlombard@redhat.com>,
	akpm@linux-foundation.org, tj@kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lib/vsprintf.c: increase the size of the field_width variable
Date: Wed, 09 Sep 2015 12:26:39 -0700	[thread overview]
Message-ID: <1441826799.17219.80.camel@perches.com> (raw)
In-Reply-To: <87mvwv4ea2.fsf@rasmusvillemoes.dk>

On Wed, 2015-09-09 at 20:51 +0200, Rasmus Villemoes wrote:
> On Wed, Sep 09 2015, Joe Perches <joe@perches.com> wrote:
> > this makes the sizeof struct printf_spec more than
> > 8 bytes which isn't desireable on x86-32.
> 
> I'm pretty sure struct printf_spec
> purposely has sizeof==8 to allow it to be (relatively cheaply) passed
> around by value.

True.  https://lkml.org/lkml/2010/3/6/141

> > %*pb is meant for smallish bitmaps, not big ones.
> 
> Yup. And that leads to my other confusion: Given that the expected
> output is given as "0-15", does the bitmap really consist of > S16_MAX
> bits with only the first 16 set?

No idea.  Tejun?

Perhaps the code in lib/vsprintf.c that sets
spec.field_width and spec.precision from format argument
input should be changed to use a temporary int and
clamped to S16_MIN -> S16_MAX.

Something like:
---
 lib/vsprintf.c | 16 ++++++++++++----
 1 file changed, 12 insertions(+), 4 deletions(-)

diff --git a/lib/vsprintf.c b/lib/vsprintf.c
index 7f0cdd2..2782129 100644
--- a/lib/vsprintf.c
+++ b/lib/vsprintf.c
@@ -1913,13 +1913,21 @@ int vsnprintf(char *buf, size_t size, const char *fmt, va_list args)
 			break;
 		}
 
-		case FORMAT_TYPE_WIDTH:
-			spec.field_width = va_arg(args, int);
+		case FORMAT_TYPE_WIDTH: {
+			int tmp = va_arg(args, int);
+
+			spec.field_width = (s16)clamp_t(int, tmp,
+							S16_MIN, S16_MAX);
 			break;
+		}
 
-		case FORMAT_TYPE_PRECISION:
-			spec.precision = va_arg(args, int);
+		case FORMAT_TYPE_PRECISION: {
+			int tmp = va_arg(args, int);
+
+			spec.precision = (s16)clamp_t(int, tmp,
+						      S16_MIN, S16_MAX);
 			break;
+		}
 
 		case FORMAT_TYPE_CHAR: {
 			char c;



  reply	other threads:[~2015-09-09 19:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-09 10:13 [PATCH] lib/vsprintf.c: increase the size of the field_width variable Maurizio Lombardi
2015-09-09 13:39 ` Tejun Heo
2015-09-09 16:33 ` Joe Perches
2015-09-09 16:36   ` Tejun Heo
2015-09-09 16:55     ` Joe Perches
2015-09-09 18:51   ` Rasmus Villemoes
2015-09-09 19:26     ` Joe Perches [this message]
2015-09-10 14:36       ` Tejun Heo
2015-09-10 15:41         ` Joe Perches
2015-09-10 15:47           ` Tejun Heo
2015-09-10  7:04     ` Maurizio Lombardi
2015-09-10  7:13       ` Maurizio Lombardi
2015-09-10  7:38       ` Joe Perches
2015-09-10  7:56         ` Rasmus Villemoes
2015-09-10  8:17           ` Joe Perches
2015-09-10 14:43             ` Tejun Heo
2015-09-10  8:39         ` Maurizio Lombardi

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=1441826799.17219.80.camel@perches.com \
    --to=joe@perches.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=mlombard@redhat.com \
    --cc=tj@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox