RESOLVED WONTFIX148423
[WebKit2] add some protection code at IndexedDB
https://bugs.webkit.org/show_bug.cgi?id=148423
Summary [WebKit2] add some protection code at IndexedDB
Jincheol Jo
Reported 2015-08-25 02:19:34 PDT
Metadata pointer seems to need a null protection code. Its member is accessed in next line. I guess it can trigger crash.
Attachments
Patch (1.86 KB, patch)
2015-08-25 02:24 PDT, Jincheol Jo
mcatanzaro: review-
Jincheol Jo
Comment 1 2015-08-25 02:24:32 PDT
Brady Eidson
Comment 2 2015-08-25 21:49:23 PDT
Are you just offering this patch because of code inspection, or do you actually have a reproducible case of the null deref crash?
Jincheol Jo
Comment 3 2015-08-26 02:51:40 PDT
(In reply to comment #2) > Are you just offering this patch because of code inspection, or do you > actually have a reproducible case of the null deref crash? When I blocked all function body code of KeyedEncoder and KeyedDecoder for my test, it triggered crash in that line.
Brady Eidson
Comment 4 2015-08-26 09:08:24 PDT
(In reply to comment #3) > (In reply to comment #2) > > Are you just offering this patch because of code inspection, or do you > > actually have a reproducible case of the null deref crash? > > When I blocked all function body code of KeyedEncoder and KeyedDecoder for > my test, it triggered crash in that line. For what test? This patch has no test. And what do you mean "blocked all function body code of KeyedEncoder and KeyedDecoder"?
Brady Eidson
Comment 5 2015-08-26 09:20:36 PDT
(In reply to comment #4) > (In reply to comment #3) > > (In reply to comment #2) > > > Are you just offering this patch because of code inspection, or do you > > > actually have a reproducible case of the null deref crash? > > > > When I blocked all function body code of KeyedEncoder and KeyedDecoder for > > my test, it triggered crash in that line. > > For what test? This patch has no test. Since I hadn't explicitly stated this, I will now - Patches require tests unless there's a darned good reason why they're untestable. It sounds like you have a way of triggering the crash, we'd like a test that triggers the crash along with the patch.
Jincheol Jo
Comment 6 2015-08-26 19:31:59 PDT
(In reply to comment #5) > (In reply to comment #4) > > (In reply to comment #3) > > > (In reply to comment #2) > > > > Are you just offering this patch because of code inspection, or do you > > > > actually have a reproducible case of the null deref crash? > > > > > > When I blocked all function body code of KeyedEncoder and KeyedDecoder for > > > my test, it triggered crash in that line. > > > > For what test? This patch has no test. > > Since I hadn't explicitly stated this, I will now - Patches require tests > unless there's a darned good reason why they're untestable. > > It sounds like you have a way of triggering the crash, we'd like a test that > triggers the crash along with the patch. (In reply to comment #5) > (In reply to comment #4) > > (In reply to comment #3) > > > (In reply to comment #2) > > > > Are you just offering this patch because of code inspection, or do you > > > > actually have a reproducible case of the null deref crash? > > > > > > When I blocked all function body code of KeyedEncoder and KeyedDecoder for > > > my test, it triggered crash in that line. > > > > For what test? This patch has no test. > > Since I hadn't explicitly stated this, I will now - Patches require tests > unless there's a darned good reason why they're untestable. > > It sounds like you have a way of triggering the crash, we'd like a test that > triggers the crash along with the patch. Thanks for quick reply, I will prepare a test.
Michael Catanzaro
Comment 7 2015-12-31 14:42:24 PST
Comment on attachment 259832 [details] Patch Removing this from the request queue, pending a testcase.
Note You need to log in before you can comment on or make changes to this bug.