New issue
Advanced search Search tips

Issue 812324 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Feb 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

CHECK failure: request_info->traffic_annotation.is_valid() in quic_http_stream.cc

Project Member Reported by ClusterFuzz, Feb 14 2018

Issue description

Detailed report: https://clusterfuzz.com/testcase?key=5711179981520896

Fuzzer: libFuzzer_net_quic_stream_factory_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  request_info->traffic_annotation.is_valid() in quic_http_stream.cc
  net::QuicHttpStream::InitializeStream
  quic_stream_factory_fuzzer.cc
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=536677:536684

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5711179981520896

Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
 
Project Member

Comment 1 by ClusterFuzz, Feb 14 2018

Components: Internals>Network>QUIC
Labels: Test-Predator-Auto-Components
Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.
Project Member

Comment 2 by ClusterFuzz, Feb 14 2018

Labels: Test-Predator-Auto-Owner
Owner: rhalavati@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/683bcaa938173f9d6bfd3506fc9dd895c91f9a39 (Add traffic annotation to QuicChromiumClientStream constructor.).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.
Status: Started (was: Assigned)
Project Member

Comment 4 by bugdroid1@chromium.org, Feb 21 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/a1256c8c08e2e0ebd3145a3e8ea1e1c659f65a19

commit a1256c8c08e2e0ebd3145a3e8ea1e1c659f65a19
Author: Ramin Halavati <rhalavati@chromium.org>
Date: Wed Feb 21 06:18:21 2018

Add traffic annotation to Quic Stream Factory Fuzzer.

Test network traffic annotation tag is added to:
net/quic/chromium/quic_stream_factory_fuzzer.cc

Bug:  812324 
Change-Id: Ic90dbace0f319ec32ad78a40f73a11c184d1338f
Reviewed-on: https://chromium-review.googlesource.com/923969
Reviewed-by: Ryan Hamilton <rch@chromium.org>
Commit-Queue: Ramin Halavati <rhalavati@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538037}
[modify] https://crrev.com/a1256c8c08e2e0ebd3145a3e8ea1e1c659f65a19/net/quic/chromium/quic_stream_factory_fuzzer.cc

Status: Fixed (was: Started)
Project Member

Comment 6 by ClusterFuzz, Feb 21 2018

ClusterFuzz has detected this issue as fixed in range 537851:537867.

Detailed report: https://clusterfuzz.com/testcase?key=5711179981520896

Fuzzer: libFuzzer_net_quic_stream_factory_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  request_info->traffic_annotation.is_valid() in quic_http_stream.cc
  net::QuicHttpStream::InitializeStream
  quic_stream_factory_fuzzer.cc
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=536677:536684
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=537851:537867

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5711179981520896

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
Project Member

Comment 7 by ClusterFuzz, Feb 21 2018

Labels: ClusterFuzz-Verified
Status: Verified (was: Fixed)
ClusterFuzz testcase 5711179981520896 is verified as fixed, so closing issue as verified.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.

Sign in to add a comment