mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Nick Piggin <npiggin@kernel.dk>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Christoph Hellwig <hch@lst.de>,
	Linus <torvalds@linux-foundation.org>
Subject: Re: linux-next: manual merge of the vfs-scale tree with Linus' tree
Date: Fri, 31 Dec 2010 11:07:53 +1100	[thread overview]
Message-ID: <20101231110753.1257bef3.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20101231105432.ee0a7488.sfr@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 2960 bytes --]

[cc'ing Christoph properly this time.  The author field in the commit in
Liunus' tree has an unqualified email address which I copy-and-pasted ...]

On Fri, 31 Dec 2010 10:54:32 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next merge of the vfs-scale tree got a conflict in
> Documentation/filesystems/Locking between commit
> b83be6f20a0e468f715b14225c9f897538dfe5ad ("update
> Documentation/filesystems/Locking") from Linus' tree and various commits
> from the vfs-scale tree.
> 
> I fixed it up (as best I could - see below) and can carry the fix as
> necessary.
> -- 
> Cheers,
> Stephen Rothwell                    sfr@canb.auug.org.au
> 
> diff --cc Documentation/filesystems/Locking
> index 7686e76,c1a7e72..0000000
> --- a/Documentation/filesystems/Locking
> +++ b/Documentation/filesystems/Locking
> @@@ -18,13 -22,15 +22,14 @@@ prototypes
>   	char *(*d_dname)((struct dentry *dentry, char *buffer, int buflen);
>   
>   locking rules:
> - 		dcache_lock	rename_lock	->d_lock	may block
> - d_revalidate:	no		no		no		yes
> - d_hash		no		no		no		yes
> - d_compare:	no		yes		no		no 
> - d_delete:	yes		no		yes		no
> - d_release:	no		no		no		yes
> - d_iput:		no		no		no		yes
>  -	none have BKL
> + 		rename_lock	->d_lock	may block	rcu-walk
> + d_revalidate:	no		no		yes		no
> + d_revalidate_rcu:no		no		yes (ref-walk)	maybe
> + d_hash		no		no		no		maybe
> + d_compare:	yes		no		no		maybe
> + d_delete:	no		yes		no		no
> + d_release:	no		no		yes		no
> + d_iput:		no		no		yes		no
>   d_dname:	no		no		no		no
>   
>   --------------------------- inode_operations --------------------------- 
> @@@ -41,11 -47,12 +46,13 @@@ ata *)
>   	int (*rename) (struct inode *, struct dentry *,
>   			struct inode *, struct dentry *);
>   	int (*readlink) (struct dentry *, char __user *,int);
>  -	int (*follow_link) (struct dentry *, struct nameidata *);
>  +	void * (*follow_link) (struct dentry *, struct nameidata *);
>  +	void (*put_link) (struct dentry *, struct nameidata *, void *);
>   	void (*truncate) (struct inode *);
> - 	int (*permission) (struct inode *, int, struct nameidata *);
> + 	int (*permission) (struct inode *, int);
> + 	int (*permission_rcu) (struct inode *, int, unsigned int);
>   	int (*check_acl)(struct inode *, int);
> + 	int (*check_acl_rcu)(struct inode *, int, unsigned int);
>   	int (*setattr) (struct dentry *, struct iattr *);
>   	int (*getattr) (struct vfsmount *, struct dentry *, struct kstat *);
>   	int (*setxattr) (struct dentry *, const char *,const void *,size_t,int);
> @@@ -74,7 -77,7 +81,8 @@@ put_link:	n
>   truncate:	yes		(see below)
>   setattr:	yes
>   permission:	no
> + permission_rcu: no (may not block if called in rcu-walk mode)
>  +check_acl:	no
>   getattr:	no
>   setxattr:	yes
>   getxattr:	no


-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

      reply	other threads:[~2010-12-31  0:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-30 23:54 linux-next: manual merge of the vfs-scale tree with the tree Stephen Rothwell
2010-12-31  0:07 ` Stephen Rothwell [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=20101231110753.1257bef3.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=npiggin@kernel.dk \
    --cc=torvalds@linux-foundation.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®