From: "Ollie Wild" <aaw@google.com>
To: "Peter Zijlstra" <a.p.zijlstra@chello.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Removing MAX_ARG_PAGES (request for comments/assistance)
Date: Tue, 24 Oct 2006 11:47:14 -0700 [thread overview]
Message-ID: <65dd6fd50610241147i70c978daueba7acf229fa5f23@mail.gmail.com> (raw)
In-Reply-To: <1161712748.24143.54.camel@taijtu>
> I'll have another look tomorrow, but I too don't have access to a funny
> platform, so I can be of limited help implementing the missing stack
> model. - that was all that is missing, right?
>
> Peter
That's the main technical item. I guess I was hoping for some more
general feedback regarding the desirability of this patch: "Yes, this
is good. Polish it off and we'll incorporate it," "No, we think the
status quo is fine," or something along those lines.
There is one point I forgot to mention. I'm not sure what to do with
the audit_bprm() function. It tries to copy the entire argument array
into a kmalloc'ed region, which isn't gonig to fly if we allow the
argument list to grow arbitrarily large.
Ollie
next prev parent reply other threads:[~2006-10-24 18:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 0:05 Ollie Wild
2006-10-11 8:00 ` Arjan van de Ven
2006-10-11 17:13 ` Ollie Wild
2006-10-11 13:14 ` Peter Zijlstra
2006-10-11 21:48 ` Ollie Wild
2006-10-24 17:48 ` Ollie Wild
[not found] ` <1161712748.24143.54.camel@taijtu>
2006-10-24 18:47 ` Ollie Wild [this message]
2006-12-29 20:03 ` [patch] remove MAX_ARG_PAGES Ingo Molnar
2006-12-29 20:49 ` Russell King
2006-12-29 21:23 ` Linus Torvalds
2006-12-29 22:20 ` Ingo Molnar
2006-12-29 21:57 ` Ingo Molnar
2007-01-01 6:58 ` Ollie Wild
2007-01-01 17:28 ` Pavel Machek
2007-01-02 18:18 ` David Howells
2007-01-02 17:52 ` Removing MAX_ARG_PAGES (request for comments/assistance) David Howells
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=65dd6fd50610241147i70c978daueba7acf229fa5f23@mail.gmail.com \
--to=aaw@google.com \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®