New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 760040 link

Starred by 2 users
Status: WontFix
Owner:
infe...@chromium.org
Closed: Oct 2017
Cc:
█ msrchandra@chromium.org
wfh@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

CHECK failure: error == EPERM || error == EUSERS || error == EINVAL || error == ENOSYS || error

Project Member Reported by ClusterFuzz, Aug 29 2017 
Detailed report: https://clusterfuzz.com/testcase?key=5402728846327808

Fuzzer: attekett_surku_fuzzer
Job Type: linux_asan_chrome_v8_arm
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  error == EPERM || error == EUSERS || error == EINVAL || error == ENOSYS || error
  logging::ErrnoLogMessage::~ErrnoLogMessage
  sandbox::Credentials::CanCreateProcessInNewUserNS
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_v8_arm&range=480776:480840

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

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for more information.

Comment 1 by msrchandra@chromium.org, Aug 29 2017

Cc: msrchandra@chromium.org
Labels: M-62 Test-Predator-Wrong
Owner: thomasanderson@chromium.org
Status: Assigned (was: Untriaged)
Predator and CL could not provide any possible suspects.
Using Code Search for the file, "credentials.cc" assigning to the concern owner.

Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/aebec0b4680564dfd5184cb288c07a2fd0ca50bd

@thomasanderson -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

Comment 2 by msrchandra@chromium.org, Aug 29 2017 

 Issue 760039  has been merged into this issue.

Comment 3 by thomasanderson@chromium.org, Aug 29 2017

Cc: thomasanderson@chromium.org
Owner: jln@chromium.org
Project Member

Comment 4 by ClusterFuzz, Sep 23 2017

Labels: -M-62 ClusterFuzz-Top-Crash ReleaseBlock-Beta M-63
Testcase 5402728846327808 is a top crash on ClusterFuzz for linux platform. Please prioritize fixing this crash.

Marking this crash as a Stable release blocker.

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

Comment 5 by jmukthavaram@chromium.org, Sep 25 2017 

jln@,
Friendly ping to get an update on this issue as it is marked as beta blocker .

Thank you..!

Comment 6 by thomasanderson@chromium.org, Sep 25 2017

Cc: jln@chromium.org
Owner: thomasanderson@chromium.org
Status: Started (was: Assigned)

Comment 7 by thomasanderson@chromium.org, Sep 25 2017

Cc: -jln@chromium.org -thomasanderson@chromium.org
Owner: infe...@chromium.org
Status: Assigned (was: Started)
over to inferno@: I think clusterfuzz had an issue filing this bug report.  The "error == EPERM || error == ..." is  bug 768115 , also reported by clusterfuzz.  The link in the original report goes to something else

Comment 8 by ajha@chromium.org, Sep 29 2017 

Gentle ping for an update on this issue marked as blocker due to top crash on CF.
Project Member

Comment 9 by ClusterFuzz, Oct 1 2017

Components: Internals>Core Internals>Sandbox
Labels: Test-Predator-AutoComponents
Automatically applying components based on information from OWNERS files. If this seems incorrect, please apply the Test-Predator-Wrong-Components label.

Comment 10 by jmukthavaram@chromium.org, Oct 5 2017 

Friendly ping to get update on this issue marked as blocker due to top crash on CF.

Thanks..!
Project Member

Comment 11 by ClusterFuzz, Oct 6 2017

Status: WontFix (was: Assigned)
ClusterFuzz testcase 5321880147066880 is flaky and no longer crashes, so closing issue.

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

Comment 12 by mbarbe...@chromium.org, Nov 7 2017

Labels: -Test-Predator-AutoComponents Test-Predator-Auto-Components
►

Sign in to add a comment