linux-kernel - linux-next: manual merge of the cel tree with the origin tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <20211213124151.2045975-1-broonie@kernel.org>
Date:   Mon, 13 Dec 2021 12:41:51 +0000
From:   broonie@...nel.org
To:     Chuck Lever <chuck.lever@...cle.com>
Cc:     "J . Bruce Fields" <bfields@...hat.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: linux-next: manual merge of the cel tree with the origin tree

Hi all,

Today's linux-next merge of the cel tree got a conflict in:

  fs/nfsd/nfs4state.c

between commit:

  2e3f00c5f29f0 ("nfsd: improve stateid access bitmask documentation")

from the origin tree and commit:

  98beab5dca06f ("nfsd: improve stateid access bitmask documentation")

from the cel 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 yGour 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.

diff --cc fs/nfsd/nfs4state.c
index f07fe7562d4dd,3214257767743..0000000000000
--- a/fs/nfsd/nfs4state.c
+++ b/fs/nfsd/nfs4state.c