From: Tejun Heo <tj@kernel.org>
To: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: Maurizio Lombardi <mlombard@redhat.com>,
joe@perches.com, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/3] fix *pbl format support
Date: Wed, 16 Sep 2015 13:45:36 -0400 [thread overview]
Message-ID: <20150916174536.GE3243@mtj.duckdns.org> (raw)
In-Reply-To: <87d1xi4kic.fsf@rasmusvillemoes.dk>
Hello,
On Wed, Sep 16, 2015 at 02:27:23PM +0200, Rasmus Villemoes wrote:
> If we want to fix the problem with 3/3, then this seems obviously
> necessary. There may be stuff we want to optimize later (for example, I
> don't think we should always make a local copy of the entire struct; if
> we're only modifying one of the fields, it's better to copy that field
> to a local variable and use that).
Yeap.
...
> I may have misread, or it might be fixable, but I really don't like
> playing these subtle games. snprintf already provides a method to
> reliably detect truncation; it is up to the user to decide whether and
> how to deal with that. But yes, this of course requires that snprintf
> actually attempted to format the entire bitmap, which in turn requires
> some way to pass the correct size all the way through to the bitmap
> formatter.
Agreed again.
> > PATCH 3 increases the size of printf_spec.field_width (from s16 to s32).
>
> I'm not yet completely convinced this is the right solution. Obviously,
> if other problems with the small .field_width size show up, this might
> be necessary, but as long as it's only the %pb formatter (and so far
> only a single user of that), I think smaller/other hammers should be
> thought about. So far I think there've been two alternatives: (1)
> reintroduce the dedicated bitmap pretty printer(s), (2) my half-ugly
> proposal allowing the user to pass struct printf_bitmap to the %pbh[l]
> specifier. I'll try to actually code up (2).
I suppose (2) could work too but we really should strive to provide
something convenient to print[fk] users. The balance here is pretty
one-sided.
Thanks.
--
tejun
next prev parent reply other threads:[~2015-09-16 17:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 9:08 Maurizio Lombardi
2015-09-16 9:08 ` [RFC PATCH 1/3] lib/vsprintf.c: Do not pass printf_spec by value on stack Maurizio Lombardi
2015-09-16 9:08 ` [RFC PATCH 2/3] lib/vsprintf.c: append "..." if the *pb[l] output has been truncated Maurizio Lombardi
2015-09-16 9:08 ` [RFC PATCH 3/3] lib/vsprintf.c: increase the size of the field_width variable Maurizio Lombardi
2015-09-16 12:27 ` [RFC PATCH 0/3] fix *pbl format support Rasmus Villemoes
2015-09-16 12:53 ` Maurizio Lombardi
2015-09-16 17:45 ` Tejun Heo [this message]
2015-09-16 20:35 ` Rasmus Villemoes
2015-09-21 14:54 ` Maurizio Lombardi
2015-09-21 16:24 ` Rasmus Villemoes
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=20150916174536.GE3243@mtj.duckdns.org \
--to=tj@kernel.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=mlombard@redhat.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
Powered by JetHome