public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/108251] false positive: null dereference
Date: Mon, 09 Jan 2023 19:41:07 +0000	[thread overview]
Message-ID: <bug-108251-4-5jW6LhSwgy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108251-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108251

--- Comment #5 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
As per comment #4 (optimization disabled), but adding: -fanalyzer-verbosity=3
makes things clearer:

../../src/null-deref-pr108251-smp_fetch_ssl_fc_has_early.c: In function
‘smp_fetch_ssl_fc_has_early’:
../../src/null-deref-pr108251-smp_fetch_ssl_fc_has_early.c:92:27: warning:
dereference of NULL ‘conn’ [CWE-476] [-Wanalyzer-null-dereference]
   92 |  smp->data.u.sint = ((conn->flags & CO_FL_EARLY_DATA) &&
      |                       ~~~~^~~~~~~
  ‘smp_fetch_ssl_fc_has_early’: events 1-2
    |
    |   78 | smp_fetch_ssl_fc_has_early(const struct arg *args, struct sample
*smp, const char *kw, void *private)
    |      | ^~~~~~~~~~~~~~~~~~~~~~~~~~
    |      | |
    |      | (1) entry to ‘smp_fetch_ssl_fc_has_early’
    |......
    |   83 |  conn = objt_conn(smp->sess->origin);
    |      |         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    |      |         |
    |      |         (2) calling ‘objt_conn’ from ‘smp_fetch_ssl_fc_has_early’
    |
    +--> ‘objt_conn’: events 3-6
           |
           |   61 | static inline struct connection *objt_conn(enum obj_type
*t)
           |      |                                  ^~~~~~~~~
           |      |                                  |
           |      |                                  (3) entry to ‘objt_conn’
           |   62 | {
           |   63 |  if (!t || *t != OBJ_TYPE_CONN)
           |      |     ~                             
           |      |     |
           |      |     (4) following ‘true’ branch (when ‘t’ is NULL)...
           |   64 |    return ((void *)0);
           |      |           ~                       
           |      |           |
           |      |           (5) ...to here
           |      |           (6) ‘0’ is NULL
           |
    <------+
    |
  ‘smp_fetch_ssl_fc_has_early’: events 7-10
    |
    |   83 |  conn = objt_conn(smp->sess->origin);
    |      |         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
    |      |         |
    |      |         (7) return of NULL to ‘smp_fetch_ssl_fc_has_early’ from
‘objt_conn’
    |   84 |  ssl = ssl_sock_get_ssl_object(conn);
    |   85 |  if (!ssl)
    |      |     ~    
    |      |     |
    |      |     (8) following ‘false’ branch (when ‘ssl’ is non-NULL)...
    |......
    |   88 |  smp->flags = 0;
    |      |  ~~~~~~~~~~~~~~
    |      |             |
    |      |             (9) ...to here
    |......
    |   92 |  smp->data.u.sint = ((conn->flags & CO_FL_EARLY_DATA) &&
    |      |                       ~~~~~~~~~~~
    |      |                           |
    |      |                           (10) dereference of NULL ‘conn’
    |

  parent reply	other threads:[~2023-01-09 19:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-29 13:26 [Bug analyzer/108251] New: " chipitsine at gmail dot com
2023-01-09 19:35 ` [Bug analyzer/108251] " dmalcolm at gcc dot gnu.org
2023-01-09 19:36 ` dmalcolm at gcc dot gnu.org
2023-01-09 19:38 ` dmalcolm at gcc dot gnu.org
2023-01-09 19:39 ` dmalcolm at gcc dot gnu.org
2023-01-09 19:41 ` dmalcolm at gcc dot gnu.org [this message]
2023-01-09 19:55 ` dmalcolm at gcc dot gnu.org
2023-03-09 21:21 ` [Bug analyzer/108251] -Wanalyzer-null-dereference false positive seen in haproxy's src/ssl_sample.c cvs-commit at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-108251-4-5jW6LhSwgy@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).