All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sherry Yang <sherryy@android.com>
Cc: linux-kernel@vger.kernel.org,
	"open list:ANDROID DRIVERS" <devel@driverdev.osuosl.org>,
	"Arve Hjønnevåg" <arve@android.com>,
	"Riley Andrews" <riandrews@android.com>,
	maco@google.com, tkjos@google.com
Subject: Re: [PATCH 2/2] android: binder: Fix null ptr dereference in debug msg
Date: Fri, 20 Oct 2017 15:42:13 +0200	[thread overview]
Message-ID: <20171020134213.GB4120@kroah.com> (raw)
In-Reply-To: <20171006201206.27073-3-sherryy@android.com>

On Fri, Oct 06, 2017 at 04:12:06PM -0400, Sherry Yang wrote:
> Don't access next->data in kernel debug message when the
> next buffer is null.
> 
> Acked-by: Arve Hjønnevåg <arve@android.com>
> Signed-off-by: Sherry Yang <sherryy@android.com>
> ---
>  drivers/android/binder_alloc.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Same here, can you rebase and resend this one against char-misc-linus
and resend?

thanks,

greg k-h

  reply	other threads:[~2017-10-20 13:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-16  5:11 [PATCH 0/2] android: binder: resolve lru, dentry and task deadlock Sherry Yang
2017-09-16  5:11 ` [PATCH 1/2] android: binder: Remove unused vma argument Sherry Yang
2017-09-16  5:11 ` [PATCH 2/2] android: binder: Don't get mm from task Sherry Yang
2017-10-06 20:12   ` Make binder shrinker static and fix null dereference Sherry Yang
2017-10-06 20:12     ` [PATCH 1/2] android: binder: Change binder_shrinker to static Sherry Yang
2017-10-06 20:12     ` [PATCH 2/2] android: binder: Fix null ptr dereference in debug msg Sherry Yang
2017-10-20 13:42       ` Greg Kroah-Hartman [this message]
2017-10-20 13:41   ` [PATCH 2/2] android: binder: Don't get mm from task Greg Kroah-Hartman

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=20171020134213.GB4120@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=arve@android.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maco@google.com \
    --cc=riandrews@android.com \
    --cc=sherryy@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 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.