| 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
| ||
|
Message-ID: <20221013095936.2dedd370@canb.auug.org.au>
Date: Thu, 13 Oct 2022 09:59:36 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Miklos Szeredi <miklos@...redi.hu>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Miklos Szeredi <mszeredi@...hat.com>
Subject: linux-next: manual merge of the fuse tree with Linus' tree
Hi all,
Today's linux-next merge of the fuse tree got a conflict in:
include/uapi/linux/fuse.h
between commit:
7d37539037c2 ("fuse: implement ->tmpfile()")
from Linus' tree and commit:
22fb2e02a194 ("fuse: add "expire only" mode to FUSE_NOTIFY_INVAL_ENTRY")
from the fuse 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 include/uapi/linux/fuse.h
index 76ee8f9e024a,1688fdea550f..000000000000
--- a/include/uapi/linux/fuse.h
+++ b/include/uapi/linux/fuse.h
@@@ -196,7 -196,7 +196,8 @@@
* - add FUSE_HAS_INODE_DAX, FUSE_ATTR_DAX
*
* 7.37
+ * - add FUSE_TMPFILE
+ * - add FUSE_EXPIRE_ONLY flag to fuse_notify_inval_entry
*/
#ifndef _LINUX_FUSE_H
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists