From: Stephen Rothwell <sfr@canb•auug.org.au>
To: "Mickaël Salaün" <mic@digikod•net>,
"Christian Brauner" <brauner@kernel•org>
Cc: Ian Kent <raven@themaw•net>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: manual merge of the landlock tree with the vfs-brauner tree
Date: Fri, 21 Nov 2025 15:30:59 +1100 [thread overview]
Message-ID: <20251121153059.48e3d2fa@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1321 bytes --]
Hi all,
Today's linux-next merge of the landlock tree got a conflict in:
include/linux/fs.h
between commit:
922a6f34c175 ("autofs: dont trigger mount if it cant succeed")
from the vfs-brauner tree and commit:
f0c02fe6ad93 ("landlock: Fix handling of disconnected directories")
from the landlock 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/linux/fs.h
index 474f728d1a6f,74e0d599e9fd..000000000000
--- a/include/linux/fs.h
+++ b/include/linux/fs.h
@@@ -2839,7 -3269,7 +2839,8 @@@ extern struct file * open_exec(const ch
/* fs/dcache.c -- generic fs support functions */
extern bool is_subdir(struct dentry *, struct dentry *);
extern bool path_is_under(const struct path *, const struct path *);
+u64 vfsmount_to_propagation_flags(struct vfsmount *mnt);
+ bool path_connected(struct vfsmount *mnt, struct dentry *dentry);
extern char *file_path(struct file *, char *, int);
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2025-11-21 4:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20251121153059.48e3d2fa@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=brauner@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mic@digikod$(echo .)net \
--cc=raven@themaw$(echo .)net \
/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