From: Theodore Tso <tytso@mit.edu>
To: Nick Piggin <npiggin@suse.de>
Cc: Mike Snitzer <snitzer@gmail.com>,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org, Kirill Korotaev <dev@openvz.org>
Subject: Re: potential regression in ext[34] call to __page_symlink()?
Date: Wed, 29 Oct 2008 11:40:14 -0400 [thread overview]
Message-ID: <20081029154014.GA23643@mit.edu> (raw)
In-Reply-To: <20081029032557.GA17624@wotan.suse.de>
On Wed, Oct 29, 2008 at 04:25:57AM +0100, Nick Piggin wrote:
>
> I was leaning towards adding a new AOP_FLAG_ there, usable just by
> filesystem code, and just to tell any helper code to clear __GFP_FS.
> That way callers won't get confused into thinking they can do
> GFP_ATOMIC writes from interrupt context or something ;) (which,
> trust me, somebody will attempt to do if it looks remotely feasible!)
Good point!!
- Ted
prev parent reply other threads:[~2008-10-29 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 0:11 potential regression in ext[34] call to __page_symlink()? Mike Snitzer
2008-10-29 2:40 ` Theodore Tso
2008-10-29 3:25 ` Nick Piggin
2008-10-29 15:40 ` Theodore Tso [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=20081029154014.GA23643@mit.edu \
--to=tytso@mit.edu \
--cc=dev@openvz.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@suse.de \
--cc=snitzer@gmail.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;
as well as URLs for NNTP newsgroup(s).