DriverDev-Devel Archive on
 help / color / Atom feed
From: Jann Horn <>
To: Hridya Valsaraju <>
Cc: "open list:ANDROID DRIVERS" <>,
	kernel-team <>,
	"Todd Kjos" <>,,
	"Greg Kroah-Hartman" <>,
	"kernel list" <>,
	"Arve Hjønnevåg" <>,
	"Joel Fernandes" <>,
	"Martijn Coenen" <>,
	"Christian Brauner" <>
Subject: Re: [PATCH] binder: prevent transactions to context manager from its own process.
Date: Mon, 14 Oct 2019 21:35:30 +0200
Message-ID: <> (raw)
In-Reply-To: <>

On Mon, Oct 14, 2019 at 7:38 PM Hridya Valsaraju <> wrote:
> On Fri, Oct 11, 2019 at 3:11 PM Jann Horn <> wrote:
> > On Fri, Oct 11, 2019 at 11:59 PM Jann Horn <> wrote:
> > > (I think you could also let A receive a handle
> > > to itself and then transact with itself, but I haven't tested that.)
> >
> > Ignore this sentence, that's obviously wrong because same-binder_proc
> > nodes will always show up as a binder, not a handle.
> Thank you for the email and steps to reproduce the issue Jann. I need
> some time to take a look at the same and I will get back to you once I
> understand it and hopefully have a fix. We do want to disallow
> same-process transactions. Here is a little bit more of context for
> the patch:

That patch (commit 7aa135fcf26377f92dc0680a57566b4c7f3e281b) prevented
transactions within one *binder_proc*, which makes sense to me; that
still allows same-process transactions, so long as they are between
different binder_proc instances. What I don't understand is your
follow-up in commit 49ed96943a8e0c62cc5a9b0a6cfc88be87d1fcec, where
you try to block transactions within the same process (well, kind of,
the semantics of the term "process" are quite fuzzy here and don't map
onto binder well).
devel mailing list

      reply index

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-15 19:18 hridya
2019-07-15 20:36 ` Todd Kjos
2019-10-11 21:59 ` Jann Horn
2019-10-11 22:11   ` Jann Horn
2019-10-14 17:37     ` Hridya Valsaraju
2019-10-14 19:35       ` Jann Horn [this message]

Reply instructions:

You may reply publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DriverDev-Devel Archive on

Archives are clonable:
	git clone --mirror driverdev-devel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 driverdev-devel driverdev-devel/ \
	public-inbox-index driverdev-devel

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone