public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/28350] ping receives SIGABRT on lib32-qemux86-64 caused by recvmsg() Date: Wed, 12 Jan 2022 13:30:40 +0000 [thread overview] Message-ID: <bug-28350-131-L0y2VfaFLW@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-28350-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=28350 --- Comment #3 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Adhemerval Zanella <azanella@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=21e0f45c7d73df6fe30c77ffcc9f81410e2ee369 commit 21e0f45c7d73df6fe30c77ffcc9f81410e2ee369 Author: Adhemerval Zanella <adhemerval.zanella@linaro.org> Date: Mon Sep 27 16:07:08 2021 -0300 linux: Fix ancillary 64-bit time timestamp conversion (BZ #28349, BZ #28350) The __convert_scm_timestamps() only updates the control message last pointer for SOL_SOCKET type, so if the message control buffer contains multiple ancillary message types the converted timestamp one might overwrite a valid message. The test check if the extra ancillary space is correctly handled by recvmsg/recvmmsg, where if there is no extra space for the 64-bit time_t converted message the control buffer should be marked with MSG_TRUNC. It also check if recvmsg/recvmmsg handle correctly multiple ancillary data. Checked on x86_64-linux and on i686-linux-gnu on both 5.11 and 4.15 kernel. Co-authored-by: Fabian Vogt <fvogt@suse.de> -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-01-12 13:30 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-18 7:08 [Bug libc/28350] New: ping " yi.zhao at windriver dot com 2021-09-22 7:26 ` [Bug libc/28350] ping receives " yi.zhao at windriver dot com 2021-09-22 10:20 ` fweimer at redhat dot com 2021-09-22 13:02 ` sam at gentoo dot org 2021-09-22 13:02 ` sam at gentoo dot org 2021-09-27 18:15 ` adhemerval.zanella at linaro dot org 2021-12-22 18:39 ` adhemerval.zanella at linaro dot org 2022-01-12 13:30 ` cvs-commit at gcc dot gnu.org [this message] 2022-01-12 13:40 ` cvs-commit at gcc dot gnu.org 2022-01-28 21:21 ` adhemerval.zanella at linaro dot 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-28350-131-L0y2VfaFLW@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: linkBe 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).