From: Christoph Hellwig <hch@infradead.org>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, miklos@szeredi.hu, hch@infradead.org
Subject: Re: [RFC][PATCH] kill do_filp_open()
Date: Thu, 27 Sep 2007 20:10:47 +0100 [thread overview]
Message-ID: <20070927191047.GA1545@infradead.org> (raw)
In-Reply-To: <20070927190823.A810E243@kernel>
On Thu, Sep 27, 2007 at 12:08:23PM -0700, Dave Hansen wrote:
>
> This kills off the almost empty do_filp_open(). However,
> let's keep filp_open() around. It does the nameidata allocation
> on the stack, and also adds the AT_FDCWD argument. I think
> that's enough to keep it around.
So why would we not want to allocate the nameidata in open_namei?
prev parent reply other threads:[~2007-09-27 19:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-27 19:08 Dave Hansen
2007-09-27 19:10 ` Christoph Hellwig [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=20070927191047.GA1545@infradead.org \
--to=hch@infradead.org \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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®