public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "siddhesh at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug nscd/29607] nscd repeatably crashes calling __strlen_avx2 when hosts cache is enabled
Date: Mon, 26 Sep 2022 20:22:11 +0000	[thread overview]
Message-ID: <bug-29607-131-KlQwRKSlgx@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29607-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29607

Siddhesh Poyarekar <siddhesh at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |siddhesh at sourceware dot org

--- Comment #13 from Siddhesh Poyarekar <siddhesh at sourceware dot org> ---
It would be nice if someone who can reproduce this can point out to the commit
that actually breaks this.  Given that it's likely not nscd, identifying the
offending patch could maybe even help come up with an independent reproducer
that doesn't need nscd.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-09-26 20:22 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-23 15:39 [Bug nscd/29607] New: " holger@applied-asynchrony.com
2022-09-23 17:19 ` [Bug nscd/29607] " holger@applied-asynchrony.com
2022-09-24  1:17 ` sam at gentoo dot org
2022-09-24  1:18 ` sam at gentoo dot org
2022-09-25 10:50 ` holger@applied-asynchrony.com
2022-09-25 11:09 ` schwab@linux-m68k.org
2022-09-25 11:13 ` holger@applied-asynchrony.com
2022-09-25 11:46 ` holger@applied-asynchrony.com
2022-09-25 12:16 ` holger@applied-asynchrony.com
2022-09-26 18:03 ` sam at gentoo dot org
2022-09-26 19:13 ` holger@applied-asynchrony.com
2022-09-26 19:20 ` holger@applied-asynchrony.com
2022-09-26 19:34 ` holger@applied-asynchrony.com
2022-09-26 19:34 ` sam at gentoo dot org
2022-09-26 19:49 ` holger@applied-asynchrony.com
2022-09-26 20:11 ` holger@applied-asynchrony.com
2022-09-26 20:22 ` siddhesh at sourceware dot org [this message]
2022-09-27  5:33 ` holger@applied-asynchrony.com
2022-09-29 23:25 ` sam at gentoo dot org
2022-09-30 18:03 ` siddhesh at sourceware dot org
2022-10-04 22:40 ` cvs-commit at gcc dot gnu.org
2022-10-04 22:44 ` cvs-commit at gcc dot gnu.org
2022-10-04 22:45 ` siddhesh at sourceware dot org
2022-10-07 14:34 ` cvs-commit at gcc dot gnu.org
2022-10-07 14:34 ` cvs-commit at gcc dot gnu.org

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=bug-29607-131-KlQwRKSlgx@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).