All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miklos Szeredi <miklos@szeredi.hu>
To: Nick Piggin <npiggin@gmail.com>
Cc: marco.stornelli@gmail.com, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: Important for fs devs: rcu-walk merged upstream
Date: Tue, 11 Jan 2011 12:08:10 +0100	[thread overview]
Message-ID: <E1Pcc5C-0007PC-LS@pomaz-ex.szeredi.hu> (raw)
In-Reply-To: <AANLkTikJjL6XEDJiYSh_J_rT+5LRUNj5EKDzCQ-852D7@mail.gmail.com> (message from Nick Piggin on Tue, 11 Jan 2011 20:57:58 +1100)

On Tue, 11 Jan 2011, Nick Piggin wrote:
> On Saturday, 8 January 2011, Marco Stornelli <marco.stornelli@gmail.com> wrote:
> > Il 08/01/2011 03:54, Nick Piggin ha scritto:
> >> The vfs-scale branch is now upstream. If you haven't
> >> looked yet, your filesystem is likely to have been
> >> touched, so check it out.
> >>
> >> Also look at Documentation/filesystems/porting and
> >> path-lookup.txt.
> >
> > Nick, in the porting file I read:
> >
> > ..........hazards on dentries and inodes (see
> > Documentation/filesystems/path-walk.txt). ..........
> >  ^^^^^^^^^^^^^
> >
> > Should it be "path-lookup.txt"?
> >
> > Marco
> >
> 
> Hi, yes thanks I'll fix it

Also you use IPERM_RCU instead of IPERM_FLAG_RCU in the documentation.

Thanks,
Miklos


diff --git a/Documentation/filesystems/porting b/Documentation/filesystems/porting
index 07a32b4..c2819ee 100644
--- a/Documentation/filesystems/porting
+++ b/Documentation/filesystems/porting
@@ -383,5 +383,5 @@ Documentation/filesystems/vfs.txt for more details.
 
 	permission and check_acl are inode permission checks that are called
 on many or all directory inodes on the way down a path walk (to check for
-exec permission). These must now be rcu-walk aware (flags & IPERM_RCU). See
-Documentation/filesystems/vfs.txt for more details.
+exec permission). These must now be rcu-walk aware (flags & IPERM_FLAG_RCU).
+See Documentation/filesystems/vfs.txt for more details.
diff --git a/Documentation/filesystems/vfs.txt b/Documentation/filesystems/vfs.txt
index fbb324e..de8a967 100644
--- a/Documentation/filesystems/vfs.txt
+++ b/Documentation/filesystems/vfs.txt
@@ -415,9 +415,9 @@ otherwise noted.
   permission: called by the VFS to check for access rights on a POSIX-like
   	filesystem.
 
-	May be called in rcu-walk mode (flags & IPERM_RCU). If in rcu-walk
-	mode, the filesystem must check the permission without blocking or
-	storing to the inode.
+	May be called in rcu-walk mode (flags & IPERM_FLAG_RCU). If in
+	rcu-walk mode, the filesystem must check the permission without
+	blocking or storing to the inode.
 
 	If a situation is encountered that rcu-walk cannot handle, return
 	-ECHILD and it will be called again in ref-walk mode.
5B5B

  reply	other threads:[~2011-01-11 11:08 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-08  2:54 Important for fs devs: rcu-walk merged upstream Nick Piggin
2011-01-08  9:10 ` Marco Stornelli
2011-01-11  9:57   ` Nick Piggin
2011-01-11  9:57     ` Nick Piggin
2011-01-11 11:08     ` Miklos Szeredi [this message]
2011-01-10 14:38 ` J. R. Okajima
2011-01-11 12:57   ` Nick Piggin
2011-01-11 12:57     ` Nick Piggin
2011-01-11  1:08 ` Joel Becker
2011-01-11 13:06   ` Nick Piggin
2011-01-11 13:06     ` Nick Piggin
2011-01-13 14:58 ` Miklos Szeredi
2011-01-13 16:18   ` Miklos Szeredi
2011-01-14  1:21     ` Nick Piggin
2011-01-14  1:21       ` Nick Piggin
2011-01-14  8:45       ` Miklos Szeredi
2011-01-14  8:45         ` Miklos Szeredi
2011-01-14  8:52         ` Nick Piggin
2011-01-14  8:52           ` Nick Piggin
2011-01-14  9:38           ` Miklos Szeredi
2011-01-14  9:38             ` Miklos Szeredi

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=E1Pcc5C-0007PC-LS@pomaz-ex.szeredi.hu \
    --to=miklos@szeredi.hu \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marco.stornelli@gmail.com \
    --cc=npiggin@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 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.