linux-kernel - linux-next: manual merge of the vfs-brauner tree with the cifs 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>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20240906084637.295241d1@canb.auug.org.au>
Date: Fri, 6 Sep 2024 08:46:37 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Christian Brauner <brauner@...nel.org>, Steve French
 <smfrench@...il.com>
Cc: CIFS <linux-cifs@...r.kernel.org>, David Howells <dhowells@...hat.com>,
 Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Linux Next
 Mailing List <linux-next@...r.kernel.org>, Steve French
 <stfrench@...rosoft.com>
Subject: linux-next: manual merge of the vfs-brauner tree with the cifs tree

Hi all,

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

  fs/smb/client/cifssmb.c

between commit:

  a68c74865f51 ("cifs: Fix SMB1 readv/writev callback in the same way as SMB2/3")

from the cifs tree and commit:

  0fda1f8c6bf8 ("netfs: Speed up buffered reading")

from the vfs-brauner tree.

I fixed it up (I used the former as it is (supposedly) a much newer patch)
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

Content of type "application/pgp-signature" skipped