Lines Matching refs:issue

14 from the developers, so the more information you can share about the issue, the
32     consider a fix as effective.  This includes both a way to trigger the issue
38     definition if an issue cannot be reproduced, it is not exploitable, thus it
61     will be credited for finding and fixing this issue.  Note that in this case
66     the issue appear. It is useful to share them, as they can be helpful to
88 reporting, consider whether the issue actually crosses a trust boundary on such
99 If you are unsure whether an issue qualifies, err on the side of reporting
111 consider the issue as being public or trivial to discover (e.g. result of a
118 exception is when an issue concerns closely related parts maintained by the
212     rare hardware or almost extinct network protocols, the issue is likely not
225 the issue is clearly trivial and publicly discoverable, you should report it
262 issue if all the details are hidden away in attachments.  Think of it like a
323 of a potential security issue you DO NOT contact the "linux-distros"
339 assigned for a confirmed issue, they can contact the :doc:`kernel CVE