From: "Dae R. Jeong" <threeearcat@gmail.com>
To: Minchan Kim <minchan@kernel.org>
Cc: gregkh@linuxfoundation.org, arve@android.com, tkjos@android.com,
maco@android.com, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: KASAN: null-ptr-deref Write in binder_update_page_range
Date: Thu, 23 Aug 2018 19:03:34 +0900 [thread overview]
Message-ID: <20180823100334.GA17523@dragonet> (raw)
In-Reply-To: <20180823052956.GA28628@rodete-desktop-imager.corp.google.com>
> Could you test this patch? I found that bug a month ago but didn't submit
> yet.
I don't have a reproducer now. I manually analzed a root cause of the
crash using a fuzzer's log. The log reported a race on 'alloc->vma'.
Because I don't have a reproducer, I can't test the patch. I'm sorry.
next prev parent reply other threads:[~2018-08-23 10:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-22 6:07 KASAN: null-ptr-deref Write in binder_update_page_range Dae R. Jeong
2018-08-23 5:29 ` Minchan Kim
2018-08-23 10:03 ` Dae R. Jeong [this message]
2018-08-24 0:36 ` Minchan Kim
2018-08-27 13:35 ` Martijn Coenen
2018-09-07 3:34 ` Minchan Kim
2018-09-12 7:18 ` Greg KH
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=20180823100334.GA17523@dragonet \
--to=threeearcat@gmail.com \
--cc=arve@android.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maco@android.com \
--cc=minchan@kernel.org \
--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 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.