On Mon, Sep 09, 2019 at 11:14:50PM +0200, John Paul Adrian Glaubitz wrote:
> On 9/9/19 10:49 PM, John Paul Adrian Glaubitz wrote:
> > Both on my Alpha XP-1000 as well as inside a qemu-user chroot, upgrading
> > glibc
> > to version 2.29-1 resulted in setuid/getuid breaking in a weird way:
>
> To
On Mon, Sep 09, 2019 at 10:49:48PM +0200, John Paul Adrian Glaubitz wrote:
> Shortly after typing "root" and pressing enter, the following message is
> printed to the
> console which seems to be an alpha-specific syscall:
>
> [ 195.414939] do_entUnaUser: 7 callbacks suppressed
No, that is not
Hi!
On 9/10/19 10:52 AM, Michael Cree wrote:
I assume this would also work on qemu-system-alpha although I haven't tried
yet. But it should work the same way but without the "--foreign" argument.
What kernel are you running? Be aware that recent kernels on alpha
(since ecf7e0a4ad15287) now
On 2019-09-09 23:16, Aurelien Jarno wrote:
> On 2019-09-09 22:49, John Paul Adrian Glaubitz wrote:
> > Source: glibc
> > Version: 2.29-1
> > Severity: important
> > User: debian-al...@lists.debian.org
> > Usertags: alpha
> >
> > Hello!
> >
> > Both on my Alpha XP-1000 as well as inside a
On 2019-09-09 22:18, Sven Joachim wrote:
> Control: tags -1 + patch
>
> On 2013-02-13 06:20 +0600, Andrey Rahmatullin wrote:
>
> > Package: libc6
> > Version: 2.17-0experimental2
> > Severity: wishlist
> >
> > Filing as wishlist, maybe it's minor or even worse for some people.
> >
> > The
Processing commands for cont...@bugs.debian.org:
> forwarded 939898 https://sourceware.org/bugzilla/show_bug.cgi?id=24986
Bug #939898 [src:glibc] glibc: setuid/getuid broken on alpha with 2.29-1
Set Bug forwarded-to-address to
'https://sourceware.org/bugzilla/show_bug.cgi?id=24986'.
> thanks
Processing control commands:
> retitle -1 glibc: new getegid, geteuid and getppid syscalls used
> unconditionally on alpha
Bug #939898 [src:glibc] glibc: setuid/getuid broken on alpha with 2.29-1
Changed Bug title to 'glibc: new getegid, geteuid and getppid syscalls used
unconditionally on
On 9/10/19 11:05 AM, John Paul Adrian Glaubitz wrote:
Yes, we have already figured out that this happens when the kernel is
too old. According to Aurelien, the problem is that the glibc package
has been built against the kernel 5.3 headers which is why users need
to upgrade their kernel first
Aurelien Jarno pushed to branch sid at GNU Libc Maintainers / glibc
Commits:
366c3309 by Sven Joachim at 2019-09-10T11:15:57Z
Do not restart services of different architecture than libc
Only check services in packages which are of the same architecture, or
arch:all. This is most easily done
On 10/09/2019 07:28, John Paul Adrian Glaubitz wrote:
> On 9/10/19 11:05 AM, John Paul Adrian Glaubitz wrote:
>> Yes, we have already figured out that this happens when the kernel is
>> too old. According to Aurelien, the problem is that the glibc package
>> has been built against the kernel
control: retitle -1 glibc: new getegid, geteuid and getppid syscalls used
unconditionally on alpha
On 2019-09-10 09:27, Adhemerval Zanella wrote:
>
>
> On 10/09/2019 07:28, John Paul Adrian Glaubitz wrote:
> > On 9/10/19 11:05 AM, John Paul Adrian Glaubitz wrote:
> >> Yes, we have already
Samuel Thibault pushed to branch sid at GNU Libc Maintainers / glibc
Commits:
43c69fdb by Samuel Thibault at 2019-09-10T21:23:57Z
patches/hurd-i386/submitted-anon-mmap-shared.diff: Re-disable
actually makes some tests fail
- - - - -
2 changed files:
- debian/changelog
-
12 matches
Mail list logo
