public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Tulio Magno Quites Machado Filho <tuliom@ascii.art.br>
To: Martin Sebor <msebor@gmail.com>, libc-alpha@sourceware.org
Cc: Florian Weimer <fweimer@redhat.com>,
	Andreas Schwab <schwab@linux-m68k.org>
Subject: Re: [PATCH] more out of bounds checking improvements
Date: Fri, 07 May 2021 16:30:35 -0300	[thread overview]
Message-ID: <87bl9mxrxg.fsf@linux.ibm.com> (raw)
In-Reply-To: <87h7je99xi.fsf@igel.home>

Andreas Schwab <schwab@linux-m68k.org> writes:

> makedb.c: In function 'write_output':
> makedb.c:797:7: error: 'writev' specified size 4294967295 exceeds maximum object size 2147483647 [-Werror=stringop-overflow=]
>   797 |   if (writev (fd, iov, iov_nelts) != keydataoffset)
>       |       ^~~~~~~~~~~~~~~~~~~~~~~~~~~
> In file included from ../include/sys/uio.h:2,
>                  from makedb.c:39:
> ../misc/sys/uio.h:52:16: note: in a call to function 'writev' declared with attribute 'read_only (2, 3)'
>    52 | extern ssize_t writev (int __fd, const struct iovec *__iovec, int __count)
>       |                ^~~~~~
> cc1: all warnings being treated as errors
> make[2]: *** [../o-iterator.mk:9: /home/abuild/rpmbuild/BUILD/glibc-2.33.9000.515.g3bf0b4f2cd/cc-base/nss/makedb.o] Error 1
> make[2]: *** Waiting for unfinished jobs....
> make[2]: Leaving directory '/home/abuild/rpmbuild/BUILD/glibc-2.33.9000.515.g3bf0b4f2cd/nss'
> make[1]: *** [Makefile:479: nss/others] Error 2
> make[1]: Leaving directory '/home/abuild/rpmbuild/BUILD/glibc-2.33.9000.515.g3bf0b4f2cd'
> make: *** [Makefile:9: all] Error 2

I'm also reproducing this on ppc32 with GCC 10.
I'm not using -DNDEBUG.

-- 
Tulio Magno

  parent reply	other threads:[~2021-05-07 19:30 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-26 15:01 Martin Sebor
2020-10-26 15:41 ` Florian Weimer
2020-12-09  0:18   ` Martin Sebor
2020-10-26 16:08 ` Joseph Myers
2020-12-09 21:46   ` Martin Sebor
2020-12-18 16:56     ` Ping: " Martin Sebor
2021-01-04 15:54       ` Ping 2: " Martin Sebor
2021-01-10 20:44         ` Ping 3: " Martin Sebor
2021-04-22 21:36           ` Ping 4: " Martin Sebor
2021-04-23 10:31     ` Florian Weimer
2021-04-23 15:06       ` Martin Sebor
2021-04-23 16:01         ` Florian Weimer
2021-05-04 19:58           ` Martin Sebor
2021-05-06 17:03             ` Martin Sebor
2021-05-06 18:15               ` Joseph Myers
2021-05-06 19:40                 ` Martin Sebor
2021-05-07  9:20               ` Andreas Schwab
2021-05-07  9:24                 ` Florian Weimer
2021-05-07 11:48                   ` Andreas Schwab
2021-05-07 19:30                 ` Tulio Magno Quites Machado Filho [this message]
2021-05-10 17:23                   ` Joseph Myers
2021-05-10  8:45               ` Florian Weimer
2021-05-10 17:14                 ` Martin Sebor
2021-05-10 17:49                   ` Florian Weimer
2021-05-10 18:37                     ` Martin Sebor
2021-05-10 19:22                       ` Andreas Schwab
2021-05-10 19:50                         ` Florian Weimer
2021-05-10 20:31                           ` Martin Sebor
2021-05-11 10:53                             ` Florian Weimer

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=87bl9mxrxg.fsf@linux.ibm.com \
    --to=tuliom@ascii.art.br \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=msebor@gmail.com \
    --cc=schwab@linux-m68k.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).