From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Anna Schumaker <anna@kernel.org>, Trond Myklebust <trondmy@gmail.com>
Cc: Christian Brauner <brauner@kernel.org>,
NFS Mailing List <linux-nfs@vger.kernel.org>,
Anna Schumaker <anna.schumaker@oracle.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Mike Snitzer <snitzer@kernel.org>
Subject: Re: linux-next: manual merge of the vfs-brauner tree with the nfs-anna tree
Date: Tue, 21 Jan 2025 10:33:56 +1100 [thread overview]
Message-ID: <20250121103356.10d8a15c@canb.auug.org.au> (raw)
In-Reply-To: <20250109084503.1e046ef7@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1588 bytes --]
Hi all,
On Thu, 9 Jan 2025 08:45:03 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next merge of the vfs-brauner tree got a conflict in:
>
> fs/nfsd/filecache.c
>
> between commit:
>
> 735aab1241ea ("nfsd: nfsd_file_acquire_local no longer returns GC'd nfsd_file")
>
> from the nfs-anna tree and commits:
>
> f905e00904cc ("tree-wide: s/revert_creds()/put_cred(revert_creds_light())/g")
> 51c0bcf0973a ("tree-wide: s/revert_creds_light()/revert_creds()/g")
>
> from the vfs-brauner 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/nfsd/filecache.c
> index 2adf95e2b379,dc5c9d8e8202..000000000000
> --- a/fs/nfsd/filecache.c
> +++ b/fs/nfsd/filecache.c
> @@@ -1255,8 -1247,8 +1255,8 @@@ nfsd_file_acquire_local(struct net *net
> __be32 beres;
>
> beres = nfsd_file_do_acquire(NULL, net, cred, client,
> - fhp, may_flags, NULL, pnf, true);
> + fhp, may_flags, NULL, pnf, false);
> - revert_creds(save_cred);
> + put_cred(revert_creds(save_cred));
> return beres;
> }
>
This is now a conflict between the nfs-anna tree and Linus' tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-01-20 23:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 21:45 linux-next: manual merge of the vfs-brauner tree with the nfs-anna tree Stephen Rothwell
2025-01-20 23:33 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-10 23:38 Stephen Rothwell
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=20250121103356.10d8a15c@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=anna.schumaker@oracle.com \
--cc=anna@kernel.org \
--cc=brauner@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=snitzer@kernel.org \
--cc=trondmy@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