From: Greg KH <greg@kroah.com>
To: Alice Ryhl <aliceryhl@google.com>
Cc: Mark Brown <broonie@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
Keshav Verma <iganschel@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the char-misc tree with the origin tree
Date: Tue, 14 Jul 2026 14:55:14 +0200 [thread overview]
Message-ID: <2026071439-magnify-submersed-b5c0@gregkh> (raw)
In-Reply-To: <alYvsW4eRWsA46YU@google.com>
On Tue, Jul 14, 2026 at 12:46:41PM +0000, Alice Ryhl wrote:
> On Mon, Jul 13, 2026 at 03:08:06PM +0100, Mark Brown wrote:
> > Hi all,
> >
> > Today's linux-next merge of the char-misc tree got conflicts in:
> >
> > drivers/android/binder/node.rs
> > drivers/android/binder/process.rs
> >
> > between commits:
> >
> > 6849cabfd30fb ("rust_binder: reject context manager self-transaction")
> > bc4a982889787 ("rust_binder: clear freeze listener on node removal")
> >
> > from the origin tree and commits:
> >
> > b9d17aa74ddd7 ("rust_binder: avoid allocating under node_refs for freeze listeners")
> > 521eae8326a18 ("rust_binder: avoid dropping NodeRef in update_ref() under lock")
> >
> > from the char-misc 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.
> >
> > I am really not at all confident in this merge.
>
> Thanks for giving it a shot! I have a slightly different resolution
> since some lines added by commit bc4a98288978 ("rust_binder: clear
> freeze listener on node removal") need to be kept.
>
> Please see below for the diff between my resolution and yours.
>
> Alice
>
>
>
> $ git diff linux-next/master drivers/android/binder
> diff --git a/drivers/android/binder/process.rs b/drivers/android/binder/process.rs
> index c5f745c85a02..0555c4bd503e 100644
> --- a/drivers/android/binder/process.rs
> +++ b/drivers/android/binder/process.rs
> @@ -954,6 +954,8 @@ pub(crate) fn update_ref(
> // increment references on itself.
> let _to_free_by_handle;
> let _to_free_by_node;
> + let _to_free_freeze_listener;
> + let _to_free_freeze_listener_cleanup;
> let mut refs = self.node_refs.lock();
> if let Some(info) = refs.by_handle.get_mut(&handle) {
> if info.node_ref().update(inc, strong) {
> @@ -971,6 +973,14 @@ pub(crate) fn update_ref(
> unsafe { info.node_ref2().node.remove_node_info(info) };
>
> let id = info.node_ref().node.global_id();
> +
> + if let Some(freeze) = *info.freeze() {
> + if let Some(fl) = refs.freeze_listeners.remove(&freeze) {
> + _to_free_freeze_listener_cleanup = fl.on_process_cleanup(&self);
> + _to_free_freeze_listener = fl;
> + }
> + }
> +
> _to_free_by_handle = refs.by_handle.remove_node(&handle);
> _to_free_by_node = refs.by_node.remove_node(&id);
> refs.handle_is_present.release_id(handle as usize);
>
That's a diff between the two, can someone provide me with the diff I
should make now to the tree when I merge these branches together?
thanks,
greg k-h
next prev parent reply other threads:[~2026-07-14 12:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 14:08 linux-next: manual merge of the char-misc tree with the origin tree Mark Brown
2026-07-14 12:46 ` Alice Ryhl
2026-07-14 12:55 ` Greg KH [this message]
2026-07-14 14:19 ` Mark Brown
2026-07-14 14:22 ` Greg KH
2026-07-14 15:06 ` Mark Brown
2026-07-14 15:14 ` Greg KH
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=2026071439-magnify-submersed-b5c0@gregkh \
--to=greg@kroah.com \
--cc=aliceryhl@google.com \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=iganschel@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.