From: Nick Piggin <npiggin@gmail.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-fsdevel@vger.kernel.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fuse: make fuse_permission() RCU aware
Date: Wed, 12 Jan 2011 15:37:32 +1100 [thread overview]
Message-ID: <AANLkTik-=LqSHQ=7zDznx9oCJFViPpp406Yz7J5Z-quj@mail.gmail.com> (raw)
In-Reply-To: <E1Pcd7R-0007XC-VO@pomaz-ex.szeredi.hu>
On Tue, Jan 11, 2011 at 11:14 PM, Miklos Szeredi <miklos@szeredi.hu> wrote:
> From: Miklos Szeredi <mszeredi@suse.cz>
>
> Only bail out of fuse_permission() on IPERM_FLAG_RCU when it is
> actually necessary.
Great, thanks for taking a look... How about d_revalidate?
next prev parent reply other threads:[~2011-01-12 4:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-11 12:14 [PATCH] fuse: make fuse_permission() RCU aware Miklos Szeredi
2011-01-12 4:37 ` Nick Piggin [this message]
2011-01-12 14:26 ` Miklos Szeredi
2011-01-13 1:49 ` Nick Piggin
2011-01-13 11:09 ` Miklos Szeredi
2011-01-13 11:16 ` Nick Piggin
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='AANLkTik-=LqSHQ=7zDznx9oCJFViPpp406Yz7J5Z-quj@mail.gmail.com' \
--to=npiggin@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).