From: Karel Zak <kzak@redhat.com>
To: Tobias Stoeckmann <tobias@stoeckmann.org>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH] rev: Avoid out of boundary read
Date: Thu, 6 Oct 2016 14:59:58 +0200 [thread overview]
Message-ID: <20161006125958.pbbrc33essqaex77@ws.net.home> (raw)
In-Reply-To: <20161003200623.GC2287@localhost>
On Mon, Oct 03, 2016 at 10:06:23PM +0200, Tobias Stoeckmann wrote:
> Check if the length of the parsed string is at least 1,
> otherwise an out of boundary read would occur.
> ---
> text-utils/rev.c | 3 +++
> 1 file changed, 3 insertions(+)
Applied, thanks.
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2016-10-06 13:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-03 20:06 [PATCH] rev: Avoid out of boundary read Tobias Stoeckmann
2016-10-06 12:59 ` Karel Zak [this message]
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=20161006125958.pbbrc33essqaex77@ws.net.home \
--to=kzak@redhat.com \
--cc=tobias@stoeckmann.org \
--cc=util-linux@vger.kernel.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 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.