From: Carlos Llamas <cmllamas@google.com>
To: Li Li <dualli@chromium.org>
Cc: dualli@google.com, corbet@lwn.net, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
donald.hunter@gmail.com, gregkh@linuxfoundation.org,
arve@android.com, tkjos@android.com, maco@android.com,
joel@joelfernandes.org, brauner@kernel.org, surenb@google.com,
arnd@arndb.de, masahiroy@kernel.org, bagasdotme@gmail.com,
horms@kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, netdev@vger.kernel.org,
hridya@google.com, smoreland@google.com, kernel-team@android.com
Subject: Re: [PATCH v11 2/2] binder: report txn errors via generic netlink
Date: Tue, 7 Jan 2025 21:41:24 +0000 [thread overview]
Message-ID: <Z32fhN6yq673YwmO@google.com> (raw)
In-Reply-To: <Z32cpF4tkP5hUbgv@google.com>
On Tue, Jan 07, 2025 at 09:29:08PM +0000, Carlos Llamas wrote:
> On Wed, Dec 18, 2024 at 12:37:40PM -0800, Li Li wrote:
> > From: Li Li <dualli@google.com>
>
> > @@ -6137,6 +6264,11 @@ static int binder_release(struct inode *nodp, struct file *filp)
> >
> > binder_defer_work(proc, BINDER_DEFERRED_RELEASE);
> >
> > + if (proc->pid == proc->context->report_portid) {
> > + proc->context->report_portid = 0;
> > + proc->context->report_flags = 0;
>
> Isn't ->portid the pid from the netlink report manager? How is this ever
> going to match a certain proc->pid here? Is this manager supposed to
> _also_ open a regular binder fd?
>
> It seems we are tying the cleanup of the netlink interface to the exit
> of the regular binder device, correct? This seems unfortunate as using
> the netlink interface should be independent.
>
> I was playing around with this patch with my own PoC and now I'm stuck:
> root@debian:~# ./binder-netlink
> ./binder-netlink: nlmsgerr No permission to set flags from 1301: Unknown error -1
>
> Is there a different way to reset the protid?
>
Furthermore, this seems to be a problem when the report manager exits
without a binder instance, we still think the report is enabled:
[ 202.821346] binder: Failed to send binder netlink message to 597: -111
[ 202.821421] binder: Failed to send binder netlink message to 597: -111
[ 202.821304] binder: Failed to send binder netlink message to 597: -111
[ 202.821306] binder: Failed to send binder netlink message to 597: -111
[ 202.821387] binder: Failed to send binder netlink message to 597: -111
[ 202.821464] binder: Failed to send binder netlink message to 597: -111
[ 202.821467] binder: Failed to send binder netlink message to 597: -111
[ 202.821344] binder: Failed to send binder netlink message to 597: -111
[ 202.822513] binder: Failed to send binder netlink message to 597: -111
[ 202.822152] binder: Failed to send binder netlink message to 597: -111
[ 202.822683] binder: Failed to send binder netlink message to 597: -111
[ 202.822629] binder: Failed to send binder netlink message to 597: -111
next prev parent reply other threads:[~2025-01-07 21:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 20:37 [PATCH v11 0/2] binder: report txn errors via generic netlink Li Li
2024-12-18 20:37 ` [PATCH v11 1/2] binderfs: add new binder devices to binder_devices Li Li
2024-12-18 20:37 ` [PATCH v11 2/2] binder: report txn errors via generic netlink Li Li
2025-01-07 21:29 ` Carlos Llamas
2025-01-07 21:41 ` Carlos Llamas [this message]
2025-01-08 0:00 ` Li Li
2025-01-08 19:07 ` Carlos Llamas
2025-01-08 19:56 ` Li Li
2025-01-08 21:59 ` Carlos Llamas
2025-01-09 18:51 ` Carlos Llamas
2025-01-09 19:30 ` Carlos Llamas
2025-01-09 19:48 ` Li Li
2025-01-09 20:13 ` Jakub Kicinski
2025-01-09 23:19 ` Carlos Llamas
2025-01-10 0:18 ` Jakub Kicinski
2025-01-14 6:01 ` Li Li
2025-01-14 18:32 ` Jakub Kicinski
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=Z32fhN6yq673YwmO@google.com \
--to=cmllamas@google.com \
--cc=arnd@arndb.de \
--cc=arve@android.com \
--cc=bagasdotme@gmail.com \
--cc=brauner@kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=dualli@chromium.org \
--cc=dualli@google.com \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=horms@kernel.org \
--cc=hridya@google.com \
--cc=joel@joelfernandes.org \
--cc=kernel-team@android.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maco@android.com \
--cc=masahiroy@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=smoreland@google.com \
--cc=surenb@google.com \
--cc=tkjos@android.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;
as well as URLs for NNTP newsgroup(s).