Processed: Re: both kernel and glibc want s64 not long (s32)
Processing control commands: > retitle -1 fix documentation of struct timespec' tv_nsec type Bug #861026 [libc6-dev] [x32] struct timespec tv_nsec has wrong type Changed Bug title to 'fix documentation of struct timespec' tv_nsec type' from '[x32] struct timespec tv_nsec has wrong type'. -- 861026: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861026 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#861026: both kernel and glibc want s64 not long (s32)
Control: retitle -1 fix documentation of struct timespec' tv_nsec type Adam Borowski [2017-04-23 23:41 +0200]: > So no matter what we'd argue as being "correct", there's no changing the ABI > of an architecture that was finalized 5 years ago. Thus, all we can do is > having GNU folks document this. Yes, that's fine too. There's a similar ambiguity around time_t anyway. > On your side, I'd do an explicit cast to (int) and "%d" -- even on amd64 the > upper bits must always be 0 (or the kernel responds with -EINVAL). That's more or less what I did in https://github.com/cockpit-project/cockpit/pull/6374/files Thanks, Martin
[glibc] annotated tag debian/2.19-18+deb8u8 created (now 824fb38)
This is an automated email from the git hooks/post-receive script. aurel32 pushed a change to annotated tag debian/2.19-18+deb8u8 in repository glibc. at 824fb38 (tag) tagging bd8c10cf317cb82e310456f1981c9db98b508718 (commit) replaces debian/2.19-18+deb8u7 tagged by Aurelien Jarno on Mon Apr 24 06:41:44 2017 +0200 - Log - tagging package glibc version debian/2.19-18+deb8u8 -BEGIN PGP SIGNATURE- iQIzBAABCgAdFiEEd0YmQqnvlP0Pdxltupx4Bh3djJsFAlj9gggACgkQupx4Bh3d jJtgBg//adWVRL8r1TNHlIzZj5CtCwsey7IXMyMaB8LPSqysD5+bQiAr721DUpfp FSs+vP2ZXYecFc5+I9glT12/1EY7oqBS0CL2vGNJgQaImIYNWKReTediZYydKAcw paTmvuS6uJ08yH9j/hnYLqE+Us1IXMIuugkZWNyHcSbO7FnX5j+o2/9UhdepbwHh W8FDs0ni8/m21VReAoeNo1KDITyB+EJtLrPvvUxCHJ8B14WYpAm3p2xQu4FjuEGZ SRItV0IlmoiO5kxxG1Pgo7RUwXvfmREaWSmqQOHGW6H+rCdUt8Lgd88NKtfWIh7w hpGYD6TOmVMNwZfAcTq5JkNkVfiHW72LdW1E5EaMVM+4yQsx1Y9uSpiInkjBooMe h3st36B/Y89RJm4d1tUGw2iwX+OQxnn9I7QpJPOxesZtxzWHtc2mTjWp89nJ7YwN W1GWJg6reL+HeYcOASBa3IIsU6B6kD1j2l+8bZbTy8Xjb+AKXjlmgZuFtSzJGh8A K+roeNW8i4HDRjlacq0yY5MRx8Bn2zF+TTLT9d5JgylMb8RU+YSx+F9SvY4LkIPH lO6GlEnPhlx0/Uk6a1hVaqy6vdUv0vggtljg6XX53pC1N1ovnSZX0Kk94on6x2YT lGk6C/xpZjQ20+Y+n3rdIuLN6enzwXYl9R2WCI6LHiI0ue9KiCk= =Ba3R -END PGP SIGNATURE- Aurelien Jarno (3): Update from upstream stable branch: patches/any/cvs-resolv-internal-qtype.diff: patch from upstream to fix a NULL pointer dereference in libresolv when receiving a T_UNSPEC internal QTYPE (CVE-2015-5180). Closes: #796106. releasing package glibc version 2.19-18+deb8u8 --- This annotated tag includes the following new commits: new bd8c10c releasing package glibc version 2.19-18+deb8u8 The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. -- Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-glibc/glibc.git
[glibc] branch jessie updated (138de87 -> bd8c10c)
This is an automated email from the git hooks/post-receive script. aurel32 pushed a change to branch jessie in repository glibc. from 138de87 patches/any/cvs-resolv-internal-qtype.diff: patch from upstream to fix a NULL pointer dereference in libresolv when receiving a T_UNSPEC internal QTYPE (CVE-2015-5180). Closes: #796106. new bd8c10c releasing package glibc version 2.19-18+deb8u8 The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: debian/changelog | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) -- Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-glibc/glibc.git
[glibc] 01/01: releasing package glibc version 2.19-18+deb8u8
This is an automated email from the git hooks/post-receive script. aurel32 pushed a commit to branch jessie in repository glibc. commit bd8c10cf317cb82e310456f1981c9db98b508718 Author: Aurelien Jarno Date: Mon Apr 24 06:41:44 2017 +0200 releasing package glibc version 2.19-18+deb8u8 --- debian/changelog | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/debian/changelog b/debian/changelog index 5a26d07..c7187e3 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,4 +1,4 @@ -glibc (2.19-18+deb8u8) UNRELEASED; urgency=medium +glibc (2.19-18+deb8u8) stable; urgency=medium [ Aurelien Jarno ] * Update from upstream stable branch: @@ -7,7 +7,7 @@ glibc (2.19-18+deb8u8) UNRELEASED; urgency=medium NULL pointer dereference in libresolv when receiving a T_UNSPEC internal QTYPE (CVE-2015-5180). Closes: #796106. - -- Aurelien Jarno Mon, 20 Feb 2017 23:30:47 +0100 + -- Aurelien Jarno Mon, 24 Apr 2017 06:41:38 +0200 glibc (2.19-18+deb8u7) stable; urgency=medium -- Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-glibc/glibc.git
Bug#861026: both kernel and glibc want s64 not long (s32)
> However, this is not. The documentation [2] defines struct timeval's "tv_nsec"
> field as "long int", so %ld is correct. But glibc seems to really define it
> as "__syscall_slong_t tv_nsec", and on x32 __syscall_slong_t appears to be
> "long long int".
> [2] https://www.gnu.org/software/libc/manual/html_node/Elapsed-Time.html
Both kernel and glibc use s64 in their ABI, and the high bits are actually
checked:
.--[ foo.c ]
#include
#include
#include
#include
int main()
{
struct timespec t;
t.tv_sec=1;
t.tv_nsec=0x1;
int ret = nanosleep(&t, 0);
printf("%d %s\n", ret, strerror(errno));
return 0;
}
`
amd64:
-1 Invalid argument
i386:
foo.c: In function ‘main’:
foo.c:10:15: warning: overflow in implicit constant conversion [-Woverflow]
t.tv_nsec=0x1;
^~~
0 Success
x32:
-1 Invalid argument
So no matter what we'd argue as being "correct", there's no changing the ABI
of an architecture that was finalized 5 years ago. Thus, all we can do is
having GNU folks document this.
On your side, I'd do an explicit cast to (int) and "%d" -- even on amd64 the
upper bits must always be 0 (or the kernel responds with -EINVAL).
It'd be interesting to see what's in arm64ilp32, though -- it's an
architecture that's in the same relation to armhf and arm64 as x32 is to
i386 and amd64, and it's about to get merged. Not in the merge window
that'll start in an hour-two from now, but possibly the next.
--
⢀⣴⠾⠻⢶⣦⠀ Meow!
⣾⠁⢠⠒⠀⣿⡁
⢿⡄⠘⠷⠚⠋⠀ Collisions shmolisions, let's see them find a collision or second
⠈⠳⣄ preimage for double rot13!
Bug#861026: [x32] struct timespec tv_nsec has wrong type
Package: libc6-dev
Version: 2.24-10
Hello,
I'm investigating cockpit's build failure on x32 [1]. It builds with
-Werror=format=2 to detect format string type errors, and compiling
| struct stat *buf)
| [...]
| return g_strdup_printf ("1:%lu-%ld.%ld",
| (unsigned long)buf->st_ino,
| buf->st_mtim.tv_sec,
| buf->st_mtim.tv_nsec);
fails like this:
> src/bridge/cockpitfsread.c: In function 'file_tag_from_stat':
> src/bridge/cockpitfsread.c:120:38: error: format '%ld' expects argument of
> type 'long int', but argument 3 has type '__time_t {aka long long int}'
> [-Werror=format=]
> return g_strdup_printf ("1:%lu-%ld.%ld",
This is a bug in the above cockpit source which I'll fix.
> src/bridge/cockpitfsread.c:120:42: error: format '%ld' expects argument of
> type 'long int', but argument 4 has type '__syscall_slong_t {aka long long
> int}' [-Werror=format=]
> return g_strdup_printf ("1:%lu-%ld.%ld",
> ^
> cc1: some warnings being treated as errors
However, this is not. The documentation [2] defines struct timeval's "tv_nsec"
field as "long int", so %ld is correct. But glibc seems to really define it
as "__syscall_slong_t tv_nsec", and on x32 __syscall_slong_t appears to be
"long long int".
Thanks,
Martin
[1]
https://buildd.debian.org/status/fetch.php?pkg=cockpit&arch=x32&ver=138-1&stamp=1491831935&raw=0
[2] https://www.gnu.org/software/libc/manual/html_node/Elapsed-Time.html
Re: Bug#856152: python-apt: FTBFS: Testsuite failure
Control: tags -1 - moreinfo
(jrtc forgot to untag this...)
On Wed, Mar 01, 2017 at 03:33:55PM +, James Clarke wrote:
> Control: reassign -1 dirmngr 2.1.18-6
> Control: retitle -1 dirmngr: Fails to resolve localhost and loopback
> addresses when only a loopback interface is available
>
> On Wed, Mar 01, 2017 at 01:31:40AM +0100, Julian Andres Klode wrote:
> > Control: severity 856152 important
> >
> > On Wed, Mar 01, 2017 at 06:39:37AM +0800, Chris Lamb wrote:
> > > retitle 856152 python-apt: FTBFS: AptKeyError: recv from
> > > 'hkp://localhost:19191' failed for
> > > '0xa1bD8E9D78F7FE5C3E65D8AF8B48AD6246925553'
> > > thanks
> > >
> > > Julian Andres Klode wrote:
> > >
> > > > Retry it. Maybe it timed out or something.
> > >
> > > I don't think this is a timeout issue, but if it is, surely the package
> > > build should be a little more reliable? :)
> >
> > Well, it's some GPG issue, we can't figure out every GPG thing.
> >
> > This works fine with an up-to-date sid chroot in sbuild, so I don't
> > really care, or well, can't reproduce it. Seems more like a pbuilder
> > related issue.
>
> So the issue here is that, by default, pbuilder runs the build in a
> separate network namespace with only a loopback interface configured.
> The loopback interface works, you can bind and connect as normal
> (otherwise this would have been found a long time ago), but getaddrinfo
> has a slightly interesting deviation from POSIX. POSIX states[1]:
It also fails on my system now since I switched from dnsmasq to
systemd-resolved. That's really annoying.
--
Debian Developer - deb.li/jak | jak-linux.org - free software dev
| Ubuntu Core Developer |
When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to ('inline'). Thank you.
