public inbox for libc-stable@sourceware.org
 help / color / mirror / Atom feed
From: Rafal Luzynski <digitalfreak@lingonborough.com>
To: Aurelien Jarno <aurelien@aurel32.net>, libc-stable@sourceware.org
Cc: Paul Eggert <eggert@cs.ucla.edu>
Subject: Re: [2.29 COMMITTED] regex: fix read overrun [BZ #24114]
Date: Tue, 01 Jan 2019 00:00:00 -0000	[thread overview]
Message-ID: <1004103621.41197.1552951132012@poczta.nazwa.pl> (raw)
In-Reply-To: <20190316223151.29219-1-aurelien@aurel32.net>

16.03.2019 23:31 Aurelien Jarno <aurelien@aurel32.net> wrote:
> [...]
> diff --git a/ChangeLog b/ChangeLog
> index 90558e434ce..fb88626efe1 100644
> --- a/ChangeLog
> +++ b/ChangeLog
> @@ -1,3 +1,11 @@
> +2019-01-31  Paul Eggert  <eggert@cs.ucla.edu>
> +
> +	regex: fix read overrun [BZ #24114]
> +	Problem found by AddressSanitizer, reported by Hongxu Chen in:
> +	https://debbugs.gnu.org/34140
> +	* posix/regexec.c (proceed_next_node):
> +	Do not read past end of input buffer.
> +

As far as I know the date in the ChangeLog should be the date
when the change was pushed to the git repository, not when the
patch was authored.  In case of the stable branches it should be
the date when it was pushed to the stable branch, not when it was
pushed to master.  Shall we change this?

Here is a correct example:

>  2019-03-13  Stefan Liebler  <stli@linux.ibm.com>
>  
>  	* elf/dl-sysdep.c (_dl_show_auxv): Remove condition and always

The same issue in 2.28 branch.

Regards,

Rafal

  parent reply	other threads:[~2019-03-18 23:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-01  0:00 Aurelien Jarno
2019-01-01  0:00 ` [2.29 COMMITTED] Record CVE-2019-9169 in NEWS and ChangeLog " Aurelien Jarno
2019-01-01  0:00 ` Rafal Luzynski [this message]
2019-01-01  0:00   ` [2.29 COMMITTED] regex: fix read overrun " Paul Eggert
2019-01-01  0:00   ` Aurelien Jarno
2019-01-01  0:00     ` Rafal Luzynski
2019-01-01  0:00   ` Florian Weimer
2019-01-01  0:00     ` Rafal Luzynski
2019-01-01  0:00       ` Florian Weimer

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=1004103621.41197.1552951132012@poczta.nazwa.pl \
    --to=digitalfreak@lingonborough.com \
    --cc=aurelien@aurel32.net \
    --cc=eggert@cs.ucla.edu \
    --cc=libc-stable@sourceware.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).