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, linux-kselftest@vger.kernel.org,
arve@android.com, maco@android.com, joel@joelfernandes.org,
tkjos@google.com, shuah@kernel.org
Subject: Re: [PATCH v3] selftests: add binderfs selftests
Date: Wed, 23 Jan 2019 12:00:52 +0100 [thread overview]
Message-ID: <20190123110052.GB22520@kroah.com> (raw)
In-Reply-To: <20190123105457.k7oobylgq6rwka55@brauner.io>
On Wed, Jan 23, 2019 at 11:54:58AM +0100, Christian Brauner wrote:
> On Thu, Jan 17, 2019 at 12:48:54PM +0100, Christian Brauner wrote:
> > This adds the promised selftest for binderfs. It will verify the following
> > things:
> > - binderfs mounting works
> > - binder device allocation works
> > - performing a binder ioctl() request through a binderfs device works
> > - binder device removal works
> > - binder-control removal fails
> > - binderfs unmounting works
> >
> > The tests are performed both privileged and unprivileged. The latter
> > verifies that binderfs behaves correctly in user namespaces.
> >
> > Cc: Todd Kjos <tkjos@google.com>
> > Signed-off-by: Christian Brauner <christian.brauner@ubuntu.com>
>
> Hey Shuah,
>
> If you're ok with the patch in its current form, can you please make
> sure that this still lands in 5.0? If at all possible I'd like to have
> all ducks in a row and release binderfs with selftests and everything.
> :)
I can take it in my tree with the other binderfs patches if I can get an
ack from Shuah.
thanks,
greg k-h
next prev parent reply other threads:[~2019-01-23 11:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 11:48 Christian Brauner
2019-01-23 10:54 ` Christian Brauner
2019-01-23 11:00 ` Greg KH [this message]
2019-01-23 14:15 ` shuah
2019-01-23 14:27 ` 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=20190123110052.GB22520@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arve@android.com \
--cc=christian@brauner.io \
--cc=devel@driverdev.osuosl.org \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=maco@android.com \
--cc=shuah@kernel.org \
--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
all inboxes | Powered by JetHome®