public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "danglin at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug network/30750] Unaligned accesses in resolver
Date: Wed, 13 Sep 2023 11:15:26 +0000 [thread overview]
Message-ID: <bug-30750-131-3DGL6VEVqg@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30750-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30750
John David Anglin <danglin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #2 from John David Anglin <danglin at gcc dot gnu.org> ---
Fixed by following commit on 2.38 and master:
commit c8fa383f4cec9cf1c0cc8ec97903c09af10286f4 (HEAD -> master, origin/master,
origin/HEAD)
Author: John David Anglin <danglin@gcc.gnu.org>
Date: Wed Sep 13 11:04:41 2023 +0000
resolv: Fix some unaligned accesses in resolver [BZ #30750]
Signed-off-by: John David Anglin <dave.anglin@bell.net>
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-09-13 11:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-13 17:52 [Bug libc/30750] New: " danglin at gcc dot gnu.org
2023-08-14 1:35 ` [Bug libc/30750] " sam at gentoo dot org
2023-08-14 1:45 ` sam at gentoo dot org
2023-08-14 1:45 ` [Bug network/30750] " sam at gentoo dot org
2023-08-15 19:55 ` deller at gmx dot de
2023-09-13 11:15 ` danglin at gcc dot gnu.org [this message]
2023-09-13 13:44 ` fweimer at redhat dot com
2023-11-01 17:00 ` matoro_bugzilla_glibc at matoro dot tk
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-30750-131-3DGL6VEVqg@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).