From: Jarod Wilson <jarod@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
linux-kernel@vger.kernel.org,
"Eric W. Biederman" <ebiederm@xmission.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Miklos Szeredi <miklos@szeredi.hu>, Zefan Li <lizefan@huawei.com>,
Oleg Nesterov <oleg@redhat.com>
Subject: Re: [PATCH] fs/proc: allow larger /proc/<pid>/cmdline output
Date: Mon, 13 Apr 2015 14:24:48 -0400 [thread overview]
Message-ID: <20150413182447.GD36803@redhat.com> (raw)
In-Reply-To: <20150410134520.06fc1a20f8b98a00fa768ca9@linux-foundation.org>
On Fri, Apr 10, 2015 at 01:45:20PM -0700, Andrew Morton wrote:
> On Fri, 10 Apr 2015 17:11:40 +0300 Alexey Dobriyan <adobriyan@gmail.com> wrote:
>
> > > Just trying to be conservative and keep people from doing anything too
> > > insane, but I didn't really have any particularly good reason beyond that
> > > for capping it. I'll remove the upper bound next iteration.
> >
> > There is no need for next iteration. Andrew has been ignoring real fix for more
> > than a month now!
>
> I haven't been ignoring it. I'm desperately hoping that the patch fairy
> will come up with something which is less large and complex :(
Shudder-inducing though it may be, I do have to say I'm quite happy with
the resulting behavior with Alexey's patch. It's both more
memory-efficient and more user-friendly, despite itself.
--
Jarod Wilson
jarod@redhat.com
prev parent reply other threads:[~2015-04-13 18:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 3:59 [PATCH] fs/proc: allow larger /proc/<pid>/cmdline output Jarod Wilson
2015-04-10 4:12 ` Andrew Morton
2015-04-10 12:18 ` Jarod Wilson
2015-04-10 14:11 ` Alexey Dobriyan
2015-04-10 14:13 ` [PATCH try #3] proc: fix PAGE_SIZE limit of /proc/$PID/cmdline Alexey Dobriyan
2015-04-10 18:01 ` Jarod Wilson
2015-04-10 22:09 ` Alexey Dobriyan
2015-04-13 18:28 ` Jarod Wilson
2015-04-13 20:23 ` Andrew Morton
2015-04-10 20:45 ` [PATCH] fs/proc: allow larger /proc/<pid>/cmdline output Andrew Morton
2015-04-13 18:24 ` Jarod Wilson [this message]
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=20150413182447.GD36803@redhat.com \
--to=jarod@redhat.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=miklos@szeredi.hu \
--cc=oleg@redhat.com \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.