mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Mickaël Salaün" <mic@digikod.net>
To: Mark Brown <broonie@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	 Linux Next Mailing List <linux-next@vger.kernel.org>,
	Paul Moore <paul@paul-moore.com>,
	 Christian Brauner <brauner@kernel.org>
Subject: Re: linux-next: manual merge of the landlock tree with the security tree
Date: Tue, 20 Oct 2026 16:19:58 +0200	[thread overview]
Message-ID: <20261020.oa9oezae6aX6@digikod.net> (raw)
In-Reply-To: <20261020.eethaeluo6eK@digikod.net>

On Tue, Oct 20, 2026 at 04:14:01PM +0200, Mickaël Salaün wrote:
> On Tue, Oct 20, 2026 at 02:40:57PM +0100, Mark Brown wrote:
> > Hi all,
> > 
> > Today's linux-next merge of the landlock tree got a conflict in:
> > 
> >   include/linux/ns/ns_common_types.h
> > 
> > between commit:
> > 
> >   436485132d236 ("Automated merge of 'lsm/dev' into 'stable-7.4'")
> 
> I cannot find this commit, is it a new one from linux-next?

Ok, it's a new commit from Paul, part of his pull request.  I guess I'll
re-create my merge commit...

> 
> I had to create a merge commit because the LSM next branch is too old,
> so I followed the previous merge resolution from linux-next, but it
> looks like today's merge commit is different than the previous ones.
> 
> > 
> > from the security tree and commit:
> > 
> >   0cbc5a0d65b05 ("Merge branch 'lsm/dev' into master")
> > 
> > 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.
> > 
> > diff --combined include/linux/ns/ns_common_types.h
> > index 47a5cfe2326a3,fddc62be3b626..0000000000000
> > --- a/include/linux/ns/ns_common_types.h
> > +++ b/include/linux/ns/ns_common_types.h
> > @@@ -116,11 -116,11 +116,11 @@@ struct ns_common 
> >   	struct dentry *stashed;
> >   	const struct proc_ns_operations *ops;
> >   	unsigned int inum;
> >  -	struct ns_tree;
> >  -	struct rcu_head ns_rcu;
> >   #ifdef CONFIG_SECURITY
> >   	void *ns_security;
> >   #endif
> >  +	struct ns_tree;
> >  +	struct rcu_head ns_rcu;
> 
> The previous merge (from yesterday and before [1]) was moving the
> ns_security at the end of the struct but this new merge commit moves it
> before the ns_tree field.  Do you know why?
> 
> [1] b6926a7ca6e5 ("Merge branch 'next' of
> https://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/lsm.git")
> 
> >   };
> >   
> >   #define to_ns_common(__ns)                                    \
> 
> 

      reply	other threads:[~2026-10-20 14:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-20 13:40 Mark Brown
2026-10-20 14:13 ` Mickaël Salaün
2026-10-20 14:19   ` Mickaël Salaün [this message]

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=20261020.oa9oezae6aX6@digikod.net \
    --to=mic@digikod.net \
    --cc=brauner@kernel.org \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=paul@paul-moore.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

all inboxes | Powered by JetHome®