Status: Untriaged
Owner: ----
CC: [email protected],  [email protected]
Labels: Type-Bug Pri-2 OS-All Area-Misc Size-Medium Coverity Fixit

New issue 17214 by [email protected]: Review FORWARD_NULL defects reported  
by Coverity in Webkit code base.
http://code.google.com/p/chromium/issues/detail?id=17214

Review FORWARD_NULL defects reported by Coverity in Webkit code base.

1. Go to Coverity Prevent web UI, following the instructions in
http://wiki.corp.google.com/twiki/bin/view/Main/ChromeCoverity

2. Select the reports of latest run, then choose FORWARD_NULL and review
the defects in Webkit code base, ignoring Chromium and all other third
party code.

3. Update the classification and Severity fields as follows after reviewing
the defects:

- Classification = Bug, Action = Fix or Ignore: real bug. Fix it if in
chrome or webkit codebase. If the defect is in other third party code,
evaluate its Severity and take actions accordingly. Either fix it or
ignore.

- Classification = Intentional, Action = Ignore: the code is correct and
the behavior is intended.

- Classification = False, Action = Fix: false positive, the code is
correct. However we can make suitable change to remove the defect.

- Classification = Uninspected, Action = Ignore: the defect is in out dated
source file and no longer exists, or the defect is in system files.

4. When fixing a serious defect, consider filing a separate bug report for
the defect. If you suspect the defect could be a security vulnerability,
please have the security team review the defect before filing a bug report.
For trivial defects, you can just use this bug report.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---

Reply via email to