From: Greg KH <gregkh@linuxfoundation.org>
To: Christian Brauner <christian@brauner.io>
Cc: tkjos@android.com, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, arve@android.com,
dan.carpenter@oracle.com, joel@joelfernandes.org,
maco@android.com, tkjos@google.com
Subject: Re: [PATCH v2 2/2] binderfs: reserve devices for initial mount
Date: Fri, 11 Jan 2019 10:18:18 +0100 [thread overview]
Message-ID: <20190111091818.GA17058@kroah.com> (raw)
In-Reply-To: <20190102113219.3716-2-christian@brauner.io>
On Wed, Jan 02, 2019 at 12:32:19PM +0100, Christian Brauner wrote:
> The binderfs instance in the initial ipc namespace will always have a
> reserve of 4 binder devices unless explicitly capped by specifying a lower
> value via the "max" mount option.
> This ensures when binder devices are removed (on accident or on purpose)
> they can always be recreated without risking that all minor numbers have
> already been used up.
>
> Cc: Todd Kjos <tkjos@google.com>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Signed-off-by: Christian Brauner <christian.brauner@ubuntu.com>
> ---
> v2:
> - patch unchanged
> v1:
> - patch introduced
> v0:
> - patch not present
> ---
> drivers/android/binderfs.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
What did you make this patch against? It doesn't apply cleanly so I
don't want to take it until we get everything synced up properly
together :(
I'll apply patch 1/2 now, can you rebase and resend this one?
thanks,
greg k-h
next prev parent reply other threads:[~2019-01-11 9:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-02 11:32 [PATCH v2 1/2] binderfs: implement "max" mount option Christian Brauner
2019-01-02 11:32 ` [PATCH v2 2/2] binderfs: reserve devices for initial mount Christian Brauner
2019-01-11 9:18 ` Greg KH [this message]
2019-01-11 10:06 ` Christian Brauner
2019-01-03 11:31 ` [PATCH v2 1/2] binderfs: implement "max" mount option Christian Brauner
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=20190111091818.GA17058@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arve@android.com \
--cc=christian@brauner.io \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maco@android.com \
--cc=tkjos@android.com \
--cc=tkjos@google.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