From: foobar <foobar@redchan.it>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: linux-sparse@vger.kernel.org
Subject: Re: [PATCH 2/2] ctags: avoid null deref
Date: Wed, 3 Jan 2018 15:55:23 +0000 [thread overview]
Message-ID: <20180103155523.2f1fa60bd0d4a9f708016f8a@redchan.it> (raw)
In-Reply-To: <20180102151116.22060-3-luc.vanoostenryck@gmail.com>
Luc, thank you for addressing this issue so quickly!
On Tue, 2 Jan 2018 16:11:16 +0100
Luc Van Oostenryck <luc.vanoostenryck@gmail.com> wrote:
> Protect the dereference of null base_type.
I wonder, maybe it would be better not to add this protection so future similar bugs can be found ?
next prev parent reply other threads:[~2018-01-03 15:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-01 22:58 sparse ctags segfaults (latest git) foobar
2018-01-02 15:11 ` [PATCH 0/2] fix crash in ctags.c Luc Van Oostenryck
2018-01-02 15:11 ` [PATCH 1/2] give a type to builtin functions Luc Van Oostenryck
2018-01-03 15:57 ` foobar
2018-01-03 16:41 ` Luc Van Oostenryck
2018-01-05 17:26 ` Christopher Li
2018-01-05 17:21 ` Christopher Li
2018-01-02 15:11 ` [PATCH 2/2] ctags: avoid null deref Luc Van Oostenryck
2018-01-03 15:55 ` foobar [this message]
2018-01-03 16:43 ` Luc Van Oostenryck
2018-01-04 17:44 ` [PATCH 0/2] fix crash in ctags.c Christopher Li
2018-01-04 17:43 ` sparse ctags segfaults (latest git) Christopher Li
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=20180103155523.2f1fa60bd0d4a9f708016f8a@redchan.it \
--to=foobar@redchan.it \
--cc=linux-sparse@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.com \
/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 NNTP newsgroup(s).