public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Florian Weimer <fweimer@redhat.com>,
	Joseph Myers <joseph@codesourcery.com>,
	libc-alpha@sourceware.org
Subject: Re: [PATCH v4 0/3] Fix {recv,send}{m}msg standard compliance (BZ#16919)
Date: Wed, 08 Jun 2016 21:05:00 -0000	[thread overview]
Message-ID: <5758888C.3070907@linaro.org> (raw)
In-Reply-To: <df8171e1-86da-e559-921a-f49446d1d0a3@redhat.com>



On 08/06/2016 17:27, Florian Weimer wrote:
> On 06/08/2016 10:18 PM, Adhemerval Zanella wrote:
>> This is the same issue in GCC BZ#71445 [1] comments and currently we can either
>> remove the compat symbol or make the interposition using symbol versions.
> 
> Ugh.
> 
>> If we decide to to remove the compat symbol I believe the only change in
>> libsanitizer or any interpose library would to be just assume recvmsg to
>> follow POSIX struct definition (in libsanitizer case to check the internal
>> structure accesses using socklen_t instead of size_t).
> 
> Let me repeat that I think we should revert the changes to struct msghdr and struct cmsghdr.  There is growing evidence that they are just too risky, and we seem to be past the threshold where we can ignore it.
> 
> Florian

I discussed briefly at IRC with Joseph and Carlos that indeed this change
might generate some localized incompatibilities, but the general idea is
this tooling issues should not prevent us to fix issues in GLIBC.

Also, I do fell a compelling way to just revert fixes only because highly
coupled tooling shows internal issues. For libsanitizer example, it already
required a lot of knowledge of GLIBC internal implementation and it also
adds a lot of hacking to circumvent some issues.  Ideally I would see
this symbol interposing to have some help of libc itself. 

      reply	other threads:[~2016-06-08 21:05 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-28 14:34 Adhemerval Zanella
2016-03-28 14:34 ` [PATCH 3/3] network: recvmmsg and sendmmsg " Adhemerval Zanella
2016-03-28 14:34 ` [PATCH 2/3] network: recvmsg and sendmsg " Adhemerval Zanella
2016-04-07  9:28   ` Szabolcs Nagy
2016-04-07 12:23     ` Adhemerval Zanella
2016-04-07  9:56   ` Florian Weimer
2016-04-07 11:37     ` Szabolcs Nagy
2016-04-07 12:29       ` Adhemerval Zanella
2016-04-21 14:01   ` Szabolcs Nagy
2016-04-21 20:07     ` Adhemerval Zanella
2016-04-22  8:04     ` Michael Kerrisk (man-pages)
2016-04-22 10:25       ` Szabolcs Nagy
2016-04-22 13:20         ` Michael Kerrisk (man-pages)
2016-04-22 13:40           ` Szabolcs Nagy
2016-04-21 17:15   ` Rich Felker
2016-05-02 19:17     ` Adhemerval Zanella
2016-06-07 13:31   ` Zack Weinberg
2016-06-07 14:21     ` Adhemerval Zanella
2016-06-08 20:15       ` Zack Weinberg
2016-06-08 20:58         ` Adhemerval Zanella
2016-06-09  3:18           ` Carlos O'Donell
2016-06-09 13:35             ` Zack Weinberg
2016-06-10 18:01               ` Carlos O'Donell
2016-06-10 18:19                 ` Joseph Myers
2016-06-10 18:45                   ` Carlos O'Donell
2016-06-10 20:17                     ` Joseph Myers
2016-06-13 14:43                       ` Carlos O'Donell
2016-06-09 14:21             ` Joseph Myers
2016-06-09 13:25           ` Zack Weinberg
2016-06-09 14:25             ` Adhemerval Zanella
2016-03-28 14:34 ` [PATCH 1/3] Adjust kernel-features.h defaults for recvmsg and sendmsg Adhemerval Zanella
2016-03-29 21:32   ` Joseph Myers
2016-03-29 21:50     ` Adhemerval Zanella
2016-03-29 21:53     ` Adhemerval Zanella
2016-03-29 22:16       ` Andreas Schwab
2016-04-01 13:51 ` [PATCH v4 0/3] Fix {recv,send}{m}msg standard compliance (BZ#16919) Adhemerval Zanella
2016-04-06 18:24   ` Adhemerval Zanella
2016-04-21 13:21     ` Adhemerval Zanella
2016-05-24 19:44       ` Adhemerval Zanella
2016-05-26 13:50         ` Joseph Myers
2016-05-26 14:23           ` Adhemerval Zanella
2016-05-26 14:37             ` Adhemerval Zanella
2016-05-27  9:13         ` Florian Weimer
2016-06-08  8:36 ` Florian Weimer
2016-06-08 12:37   ` Joseph Myers
2016-06-08 15:57     ` Mike Frysinger
2016-06-08 19:45       ` Florian Weimer
2016-06-08 20:19         ` Adhemerval Zanella
2016-06-08 20:27           ` Florian Weimer
2016-06-08 21:05             ` Adhemerval Zanella [this message]

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=5758888C.3070907@linaro.org \
    --to=adhemerval.zanella@linaro.org \
    --cc=fweimer@redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@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).