archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <>
To: Claire Jensen <>
Subject: Re: [PATCH 1/2] libtraceevent: Add eof checks.
Date: Thu, 17 Jun 2021 15:58:28 -0400	[thread overview]
Message-ID: <20210617155828.4e9c7f45@gandalf.local.home> (raw)
In-Reply-To: <>

On Thu, 17 Jun 2021 19:43:25 +0000
Claire Jensen <> wrote:

Hi Claire,

Thanks for sending the patches, I'll try to get some time to look at them
(note, that I have a lot of other duties that I need to finish before I can
get to this).

> Added checking for __read_char and peek_char to make sure value is not at end
> of file.
> This issue was found while fuzz testing. One of the test cases created an infinite loop because __read_token had reached end of file. Checking was added to all cases where this may occur.

You don't need to fix this now, but for future reference, we follow the
Linux guidelines on submitting patches which includes having line breaks at
74 (although I use 76) bytes, for the change log.

This makes the change logs easier to read.


-- Steve

> Signed-off-by: Claire Jensen <>

  parent reply	other threads:[~2021-06-17 19:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-17 19:43 Claire Jensen
2021-06-17 19:43 ` [PATCH 2/2] libtraceevent: Changed angled brackets to double quotes Claire Jensen
2021-06-17 19:58 ` Steven Rostedt [this message]
2021-06-24  1:06   ` [PATCH 1/2] libtraceevent: Add eof checks Steven Rostedt
2021-06-24  5:50     ` Ian Rogers
2021-06-24 13:14       ` Steven Rostedt
  -- strict thread matches above, loose matches on Subject: below --
2021-06-12  1:44 [PATCH 0/2] Build and fuzzing related fixes Ian Rogers
2021-06-12  1:45 ` [PATCH 1/2] libtraceevent: Add eof checks Ian Rogers
2021-06-13 23:30   ` Steven Rostedt
     [not found]     ` <>
2021-06-17 19:01       ` Steven Rostedt

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:

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

  git send-email \
    --in-reply-to=20210617155828.4e9c7f45@gandalf.local.home \ \ \ \ \ \ \
    --subject='Re: [PATCH 1/2] libtraceevent: Add eof checks.' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
on how to clone and mirror all data and code used for this inbox