From: Andrew Morton <akpm@linux-foundation.org>
To: Kees Cook <keescook@chromium.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Paul Wise <pabs3@bonedaddy.net>, Ingo Molnar <mingo@kernel.org>,
Rik van Riel <riel@redhat.com>,
David Rientjes <rientjes@google.com>,
Aaron Tomlin <atomlin@redhat.com>,
Dario Faggioli <raistlin@linux.it>,
Andi Kleen <ak@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>, Jens Axboe <axboe@fb.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: [PATCH] sysctl: terminate strings also on \r
Date: Thu, 23 Oct 2014 11:23:14 -0700 [thread overview]
Message-ID: <20141023112314.8d62733c202a527b4107eb11@linux-foundation.org> (raw)
In-Reply-To: <CAGXu5jL-6sGy2QSH39Qmu0-8MEg6aX5GCPvPKeWaheXcai0TDA@mail.gmail.com>
On Thu, 23 Oct 2014 09:39:09 -0700 Kees Cook <keescook@chromium.org> wrote:
> > I wonder if the chances of damage would be lower if we were to continue
> > to accept the \r, but turn it into something else ("\r"?) when it is
> > read.
>
> I think that would complicate things more than help them.
Why.
> If there's a
> legit use of \r, I'll let Paul Wise debate how to proceed. :)
I don't know who Paul is. Please take this seriously; we don't want to
have to revert this after breaking a bunch of people's setups.
next prev parent reply other threads:[~2014-10-23 18:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-21 20:21 Kees Cook
2014-10-22 10:03 ` Aaron Tomlin
2014-10-22 13:39 ` Paul E. McKenney
2014-10-22 22:49 ` David Rientjes
2014-10-22 23:26 ` Andrew Morton
2014-10-22 23:43 ` Kees Cook
2014-10-23 2:00 ` Andrew Morton
2014-10-23 16:39 ` Kees Cook
2014-10-23 18:23 ` Andrew Morton [this message]
2014-10-23 18:50 ` Kees Cook
2014-10-27 9:56 ` Pavel Machek
2014-10-27 10:11 ` Geert Uytterhoeven
2014-10-27 12:01 ` Pavel Machek
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=20141023112314.8d62733c202a527b4107eb11@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ak@linux.intel.com \
--cc=atomlin@redhat.com \
--cc=axboe@fb.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=pabs3@bonedaddy.net \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=raistlin@linux.it \
--cc=riel@redhat.com \
--cc=rientjes@google.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
all inboxes | Powered by JetHome®