From: Joe Perches <joe@perches.com>
To: Kees Cook <keescook@chromium.org>
Cc: "Jiri Slaby" <jslaby@suse.cz>,
"Tetsuo Handa" <penguin-kernel@i-love.sakura.ne.jp>,
"Al Viro" <viro@zeniv.linux.org.uk>,
"Pavel Emelyanov" <xemul@openvz.org>,
"Rémi Denis-Courmont" <remi.denis-courmont@nokia.com>,
LKML <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org, linux-sctp@vger.kernel.org,
"George Spelvin" <linux@horizon.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Dan Carpenter" <dan.carpenter@oracle.com>,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
"Jan Beulich" <JBeulich@suse.com>,
"Motohiro KOSAKI" <kosaki.motohiro@gmail.com>
Subject: Re: [PATCH 1/2] remove all uses of printf's %n
Date: Fri, 20 Sep 2013 12:33:16 -0700 [thread overview]
Message-ID: <1379705596.2301.17.camel@joe-AO722> (raw)
In-Reply-To: <CAGXu5jLENb+x6b9XOY7-pWMT7GsFgnLr0=A8VNFLkqMi0BX4=w@mail.gmail.com>
On Fri, 2013-09-20 at 12:24 -0700, Kees Cook wrote:
> There are a few problems that have been discussed on the various
> threads. Namely, we want to minimize the changes to the seq_file
> structure and to not add additional work to all the seq_file users
> that don't care about padding.
I don't think saving a couple more values to a struct
is that big a deal.
next prev parent reply other threads:[~2013-09-20 19:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAGXu5jL+NeBw2_vXymM81UdtS6UO7KZA2S4rf3gwM_7nSJ2h6g@mail.gmail.com>
[not found] ` <20130917205742.16147.qmail@science.horizon.com>
[not found] ` <201309191756.BCF65661.MQFOLSJOFHFtOV@I-love.SAKURA.ne.jp>
[not found] ` <CAGXu5jK_D1BJOQr=1A-UFrpM5Ad+Qu894HT_XjkZh4EmsbCkTQ@mail.gmail.com>
2013-09-20 4:09 ` [PATCH 1/2] remove all uses of printf's %n Tetsuo Handa
2013-09-20 4:23 ` Joe Perches
2013-09-20 4:53 ` Kees Cook
2013-09-20 8:08 ` Jiri Slaby
2013-09-20 19:24 ` Kees Cook
2013-09-20 19:33 ` Joe Perches [this message]
2013-09-21 0:28 ` Tetsuo Handa
2013-09-22 8:09 ` George Spelvin
2013-09-22 8:16 ` Geert Uytterhoeven
2013-09-23 21:24 ` Kees Cook
2013-09-30 8:16 ` Tetsuo Handa
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=1379705596.2301.17.camel@joe-AO722 \
--to=joe@perches.com \
--cc=JBeulich@suse.com \
--cc=akpm@linux-foundation.org \
--cc=dan.carpenter@oracle.com \
--cc=geert@linux-m68k.org \
--cc=jslaby@suse.cz \
--cc=keescook@chromium.org \
--cc=kosaki.motohiro@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=linux@horizon.com \
--cc=netdev@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=remi.denis-courmont@nokia.com \
--cc=viro@zeniv.linux.org.uk \
--cc=xemul@openvz.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