Re: [2.27 COMMITTED] NEWS: add entries for bugs 17343, 20419, 22644, 22786, 22884, 22947, 23005, 23037, 23069, 23137

Re: [2.27 COMMITTED] NEWS: add entries for bugs 17343, 20419, 22644, 22786, 22884, 22947, 23005, 23037, 23069, 23137

[Rafal Luzynski]

11.05.2018 14:26 "Dmitry V. Levin" <ldv@altlinux.org> wrote:
> [...]
> I don't think we are going to cut releases from 2.27 branch,
> but I don't mind backporting your fix now rather than later.

Thank you for committing.  I misunderstood that maybe 2.27.1 is going
to be released right now, before I am able to backport the patch
on my own.

Thank you Dmitry and Carlos for explaining the details about the
updates of the stable branch.  And sorry for the noise.

Regards,

Rafal

Re: [2.27 COMMITTED] NEWS: add entries for bugs 17343, 20419, 22644, 22786, 22884, 22947, 23005, 23037, 23069, 23137

[Carlos O'Donell]

On 05/11/2018 08:26 AM, Dmitry V. Levin wrote:
> On Fri, May 11, 2018 at 01:02:10PM +0200, Rafal Luzynski wrote:
>> Dmitry,
>>
>> Does this batch of backported bugfixes mean that you are
>> preparing for 2.27.1 official release, maybe today?  If yes
>> then please also accept my recent patch. [1][2] It's trivial and
>> would be nice to have it backported.  I will appreciate if you
>> commit it for me since I'm out of time atm.
> 
> I don't think we are going to cut releases from 2.27 branch,
> but I don't mind backporting your fix now rather than later.

There is no official point release process.

We expect the distros to sync from the release branch if they want
the latest fixes.

We only produce official minor releases e.g. 2.28, and even then
just to provide official tarballs for projects that still follow
that kind of process (it helps our logical process flow forward
in a time boxed fasion with useful names for groups of changes).

-- 
Cheers,
Carlos.

Re: [2.27 COMMITTED] NEWS: add entries for bugs 17343, 20419, 22644, 22786, 22884, 22947, 23005, 23037, 23069, 23137

[Rafal Luzynski]

Dmitry,

Does this batch of backported bugfixes mean that you are
preparing for 2.27.1 official release, maybe today?  If yes
then please also accept my recent patch. [1][2] It's trivial and
would be nice to have it backported.  I will appreciate if you
commit it for me since I'm out of time atm.

Regards,

Rafal


[1] https://sourceware.org/ml/libc-stable/2018-05/msg00000.html
[2] https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=bb066cb

[2.27 COMMITTED] NEWS: add entries for bugs 17343, 20419, 22644, 22786, 22884, 22947, 23005, 23037, 23069, 23137

[Dmitry V. Levin]

---
 NEWS | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/NEWS b/NEWS
index 4749f5f..6839154 100644
--- a/NEWS
+++ b/NEWS
@@ -17,22 +17,35 @@ The following bugs are resolved with this release:
 
   [6889] 'PWD' mentioned but not specified
   [16335] Feature test macro documentation incomplete and out of date
+  [17343] Signed integer overflow in /stdlib/random_r.c
+  [20419] files with large allocated notes crash in open_verify
   [21269] i386 sigaction sa_restorer handling is wrong
   [22342] NSCD not properly caching netgroup
   [22638] sparc: static binaries are broken if glibc is built by gcc
     configured with --enable-default-pie
+  [22644] memmove-sse2-unaligned on 32bit x86 produces garbage when crossing
+    2GB threshold
   [22735] Misleading typo in time.h source comment regarding CLOCKS_PER_SECOND
+  [22786] Stack buffer overflow in realpath() if input size is close
+    to SSIZE_MAX
   [22797] Linux: use reserved name __key in pkey_get
   [22807] PTRACE_* constants missing for powerpc
   [22818] posix/tst-glob_lstat_compat failure on alpha
   [22827] RISC-V ELF64 parser mis-reads flag in ldconfig
   [22848] ca_ES: update date definitions from CLDR
+  [22884] RISCV fmax/fmin handle signalling NANs incorrectly
   [22918] multiple common of `__nss_shadow_database'
   [22919] sparc32: backtrace yields infinite backtrace with makecontext
   [22926] FTBFS on powerpcspe
   [22932] lt_LT: Update of abbreviated month names from CLDR required
   [22937] Greek (el_GR, el_CY) locales actually need ab_alt_mon
+  [22947] FAIL: misc/tst-preadvwritev2
   [22963] cs_CZ: Add alternative month names
+  [23005] Crash in __res_context_send after memory allocation failure
+  [23037] initialize msg_flags to zero for sendmmsg() calls
+  [23069] sigaction broken on riscv64-linux-gnu
+  [23137] s390: pthread_join sometimes block indefinitely (on 31bit and libc
+    build with -Os)
 
 \f
 Version 2.27
-- 
ldv

Re: [2.27 COMMITTED] NEWS: add entries for bugs 17343, 20419, 22644, 22786, 22884, 22947, 23005, 23037, 23069, 23137

[Dmitry V. Levin]

[-- Attachment #1: Type: text/plain, Size: 535 bytes --]

On Fri, May 11, 2018 at 01:02:10PM +0200, Rafal Luzynski wrote:
> Dmitry,
> 
> Does this batch of backported bugfixes mean that you are
> preparing for 2.27.1 official release, maybe today?  If yes
> then please also accept my recent patch. [1][2] It's trivial and
> would be nice to have it backported.  I will appreciate if you
> commit it for me since I'm out of time atm.

I don't think we are going to cut releases from 2.27 branch,
but I don't mind backporting your fix now rather than later.

Thanks,


-- 
ldv

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]