[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201309210928.JCF90671.OtOFLFQSOJVFMH@I-love.SAKURA.ne.jp>
Date: Sat, 21 Sep 2013 09:28:14 +0900
From: Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
To: keescook@...omium.org, jslaby@...e.cz
Cc: viro@...iv.linux.org.uk, xemul@...nvz.org,
remi.denis-courmont@...ia.com, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org, linux-sctp@...r.kernel.org,
linux@...izon.com, akpm@...ux-foundation.org,
dan.carpenter@...cle.com, geert@...ux-m68k.org, JBeulich@...e.com,
joe@...ches.com, kosaki.motohiro@...il.com
Subject: Re: [PATCH 1/2] remove all uses of printf's %n
Kees Cook wrote:
> >> - seq_printf(seq, "%*s\n", 127 - len, "");
> >> + seq_pad(seq, '\n');
> >
> > Hmm, seq_pad is unintuitive. I would say it pads the string by '\n'. Of
> > course it does not, but...
>
> I don't think this is a very serious problem. Currently, the padding
> character is always ' ' for all existing callers, so it only makes
> sense to make the trailing character an argument.
If you want, we can rename seq_pad() to seq_pad_and_putc(). Also we can pass
both the padding character (e.g. ' ') and the trailing character (e.g. '\n')
like seq_pad_and_putc((' ' << 8) | '\n'), though I wonder someone wants to
use '\0', '\t', '\n' etc. as the padding character...
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists