From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Al Viro <viro@ZenIV•linux.org.uk>, Mike Marshall <hubcap@omnibond•com>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Martin Brandenburg <martin@omnibond•com>
Subject: Re: linux-next: manual merge of the vfs tree with the orangefs tree
Date: Wed, 8 May 2019 11:02:55 +1000 [thread overview]
Message-ID: <20190508110255.52ce2558@canb.auug.org.au> (raw)
In-Reply-To: <20190503111510.6e866e3b@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 2925 bytes --]
Hi all,
On Fri, 3 May 2019 11:15:10 +1000 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> Today's linux-next merge of the vfs tree got a conflict in:
>
> fs/orangefs/super.c
>
> between commit:
>
> 77becb76042a ("orangefs: implement xattr cache")
>
> from the orangefs tree and commit:
>
> f276ae0dd6d0 ("orangefs: make use of ->free_inode()")
>
> from the vfs tree.
>
> I fixed it up (see below) and can carry the fix as necessary. This
> is now fixed as far as linux-next is concerned, but any non trivial
> conflicts should be mentioned to your upstream maintainer when your tree
> is submitted for merging. You may also want to consider cooperating
> with the maintainer of the conflicting tree to minimise any particularly
> complex conflicts.
>
> --
> Cheers,
> Stephen Rothwell
>
> diff --cc fs/orangefs/super.c
> index 8fa30c13b7ed,3784f7e8b603..000000000000
> --- a/fs/orangefs/super.c
> +++ b/fs/orangefs/super.c
> @@@ -125,20 -124,9 +125,19 @@@ static struct inode *orangefs_alloc_ino
> return &orangefs_inode->vfs_inode;
> }
>
> - static void orangefs_i_callback(struct rcu_head *head)
> + static void orangefs_free_inode(struct inode *inode)
> {
> - struct inode *inode = container_of(head, struct inode, i_rcu);
> - kmem_cache_free(orangefs_inode_cache, ORANGEFS_I(inode));
> + struct orangefs_inode_s *orangefs_inode = ORANGEFS_I(inode);
> + struct orangefs_cached_xattr *cx;
> + struct hlist_node *tmp;
> + int i;
> +
> + hash_for_each_safe(orangefs_inode->xattr_cache, i, tmp, cx, node) {
> + hlist_del(&cx->node);
> + kfree(cx);
> + }
> +
> + kmem_cache_free(orangefs_inode_cache, orangefs_inode);
> }
>
> static void orangefs_destroy_inode(struct inode *inode)
> @@@ -148,17 -136,8 +147,15 @@@
> gossip_debug(GOSSIP_SUPER_DEBUG,
> "%s: deallocated %p destroying inode %pU\n",
> __func__, orangefs_inode, get_khandle_from_ino(inode));
> -
> - call_rcu(&inode->i_rcu, orangefs_i_callback);
> }
>
> +static int orangefs_write_inode(struct inode *inode,
> + struct writeback_control *wbc)
> +{
> + gossip_debug(GOSSIP_SUPER_DEBUG, "orangefs_write_inode\n");
> + return orangefs_inode_setattr(inode);
> +}
> +
> /*
> * NOTE: information filled in here is typically reflected in the
> * output of the system command 'df'
> @@@ -316,8 -295,8 +313,9 @@@ void fsid_key_table_finalize(void
>
> static const struct super_operations orangefs_s_ops = {
> .alloc_inode = orangefs_alloc_inode,
> + .free_inode = orangefs_free_inode,
> .destroy_inode = orangefs_destroy_inode,
> + .write_inode = orangefs_write_inode,
> .drop_inode = generic_delete_inode,
> .statfs = orangefs_statfs,
> .remount_fs = orangefs_remount_fs,
This is now a conflict between the orangefs tree and Linus' tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-05-08 1:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-03 1:15 linux-next: manual merge of the vfs tree with the orangefs tree Stephen Rothwell
2019-05-03 17:34 ` Mike Marshall
2019-05-03 22:26 ` Stephen Rothwell
2019-05-08 1:02 ` 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=20190508110255.52ce2558@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=hubcap@omnibond$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=martin@omnibond$(echo .)com \
--cc=viro@ZenIV$(echo .)linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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