From: Eli Zaretskii <eliz@gnu.org>
To: Yuan Fu <casouri@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Some issues with the tree-sitter branch
Date: Mon, 17 Oct 2022 09:48:49 +0300 [thread overview]
Message-ID: <83y1tf2be6.fsf@gnu.org> (raw)
In-Reply-To: <6F240F48-E29C-4E75-B5D5-30C7CF7956C9@gmail.com> (message from Yuan Fu on Sun, 16 Oct 2022 21:53:06 -0700)
> From: Yuan Fu <casouri@gmail.com>
> Date: Sun, 16 Oct 2022 21:53:06 -0700
> Cc: emacs-devel@gnu.org
>
> > . Several places assign EMACS_INT values to uint32_t variables with
> > an explicit range check (and error signal in case of overflow).
>
> I think you meant the lack of a range check? Like mentioned here:
>
> + /* FIXME: We should signal an error below if START_BYTE
> + etc. overflow the 32-bit unsigned data type. */
Yes, I added FIXME comments to make it easier to find those places.
> I added buffer size check at parser creation time, and used casts to uint32_t liberally, assuming the values never overflows and, so we don’t need to handle the error at a million places. But I should have added checks in ts_after_chang and other places where buffer size could change. I’ll add checks in ts_after_change and other places, and if the argumetns overflows uint32, it will set a flag (say, buffer_too_large) in the parser object, and next time any lisp function tries to use that parser, an buffer-too-large error will be signaled. WDYT?
That sounds fine to me, but I think we also should do something when
some value that can be larger than UINT_MAX is passed to tree-sitter
functions, because doing so might cause tree-sitter do something for a
completely unrelated portion of the buffer. At the very least add
eassert there, so that at least a build with --enable-checking will
detect such cases.
> I see that you fixed them, I’ll keep those in mind in the future. That’s a lot of lines you need to change, sorry about that :-(
That was a low-hanging fruit that was easy to pluck ;-)
next prev parent reply other threads:[~2022-10-17 6:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-16 13:32 Some issues with the tree-sitter branch Eli Zaretskii
2022-10-16 14:01 ` Eli Zaretskii
2022-10-16 15:10 ` Eli Zaretskii
2022-10-16 19:36 ` tree-sitter: Paths used for loading of language definitions Jostein Kjønigsen
2022-10-16 20:12 ` Daniel Martín
2022-10-17 4:27 ` Yuan Fu
2022-10-17 7:14 ` Jostein Kjønigsen
2022-10-17 7:29 ` Yuan Fu
2022-10-17 8:02 ` Eli Zaretskii
2022-10-17 9:02 ` Yuan Fu
2022-10-17 9:08 ` Eli Zaretskii
2022-10-17 11:56 ` Stephen Leake
2022-10-17 13:39 ` Eli Zaretskii
2022-10-17 21:15 ` Yuan Fu
2022-10-17 4:53 ` Some issues with the tree-sitter branch Yuan Fu
2022-10-17 5:37 ` Po Lu
2022-10-17 5:48 ` Yuan Fu
2022-10-17 6:48 ` Eli Zaretskii [this message]
2022-10-17 9:12 ` Yuan Fu
2022-10-17 10:14 ` Eli Zaretskii
2022-10-18 0:15 ` Yuan Fu
2022-10-18 0:14 ` Yuan Fu
2022-10-18 16:11 ` Eli Zaretskii
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=83y1tf2be6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=casouri@gmail.com \
--cc=emacs-devel@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.