Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #56060 > unrolled thread

Bug#843128: partially solved

Started byRicardo Fabian Peliquero <zhana@lasampa.com.ar>
First post2016-12-09 05:30 +0100
Last post2016-12-19 12:20 +0100
Articles 4 — 3 participants

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#843128: partially solved Ricardo Fabian Peliquero <zhana@lasampa.com.ar> - 2016-12-09 05:30 +0100
    Bug#843128: partially solved Ben Hutchings <ben@decadent.org.uk> - 2016-12-09 14:10 +0100
      Bug#843128: partially solved Ricardo Fabian Peliquero <zhana@lasampa.com.ar> - 2016-12-09 17:40 +0100
      Bug#843128: partially solved Didier 'OdyX' Raboud <odyx@debian.org> - 2016-12-19 12:20 +0100

#56060 — Bug#843128: partially solved

FromRicardo Fabian Peliquero <zhana@lasampa.com.ar>
Date2016-12-09 05:30 +0100
SubjectBug#843128: partially solved
Message-ID<sMkYN-75X-1@gated-at.bofh.it>
Dear Maintainer,

After upgrading

 from: linux-image-4.8.0-1-amd64-unsigned:amd64 (4.8.5-1)
   to: linux-image-4.9.0-rc8-amd64-unsigned:amd64 (4.9~rc8-1~exp1)

and installing mingetty(8)

the system is booting well (e.g. without kernel panic).

But the following errors appeared for ttys using these lines in /etc/inittab:

2:23:respawn:/sbin/fgetty tty2
# Produces error. Output:
 [   14.741345] fgetty[1309] vsyscall attempted with vsyscall=none ip:ffffffffff600400 cs:33 sp:7ffcb7dbade0 ax:ff[   14.753469] fgetty[1309]: segfault at ffffffffff600400 ip ffffffffff600400 sp 00007ffcb7dbade0 error 15
 [   14.761442] fgetty[1314] vsyscall attempted with vsyscall=none ip:ffffffffff600400 cs:33 sp:7ffc57494eb0 ax:ff[   14.774655] fgetty[1314]: segfault at ffffffffff600400 ip ffffffffff600400 sp 00007ffc57494eb0 error 15
 [   14.783045] fgetty[1315] vsyscall attempted with vsyscall=none ip:ffffffffff600400 cs:33 sp:7fff4cd23c40 ax:ff[   14.797132] fgetty[1315]: segfault at ffffffffff600400 ip ffffffffff600400 sp 00007fff4cd23c40 error 15
 [   14.805678] fgetty[1316] vsyscall attempted with vsyscall=none ip:ffffffffff600400 cs:33 sp:7ffebc275580 ax:ff[   14.820255] fgetty[1316]: segfault at ffffffffff600400 ip ffffffffff600400 sp 00007ffebc275580 error 15
 [   14.829085] fgetty[1317] vsyscall attempted with vsyscall=none ip:ffffffffff600400 cs:33 sp:7ffdf2ba87d0 ax:ff[   14.846203] fgetty[1317]: segfault at ffffffffff600400 ip ffffffffff600400 sp 00007ffdf2ba87d0 error 15
 [   14.855785] fgetty[1318] vsyscall attempted with vsyscall=none ip:ffffffffff600400 cs:33 sp:7fff05d8bca0 ax:ff[   14.873951] fgetty[1318]: segfault at ffffffffff600400 ip ffffffffff600400 sp 00007fff05d8bca0 error 15
 [   14.883984] fgetty[1319] vsyscall attempted with vsyscall=none ip:ffffffffff600400 cs:33 sp:7ffdb25fe940 ax:ff[   14.903582] fgetty[1319]: segfault at ffffffffff600400 ip ffffffffff600400 sp 00007ffdb25fe940 error 15
 [   14.914209] fgetty[1320] vsyscall attempted with vsyscall=none ip:ffffffffff600400 cs:33 sp:7ffe39d6bda0 ax:ff[   14.934960] fgetty[1320]: segfault at ffffffffff600400 ip ffffffffff600400 sp 00007ffe39d6bda0 error 15
 [   14.946825] fgetty[1321] vsyscall attempted with vsyscall=none ip:ffffffffff600400 cs:33 sp:7fff000656c0 ax:ff[   14.968608] fgetty[1321]: segfault at ffffffffff600400 ip ffffffffff600400 sp 00007fff000656c0 error 15
 [   14.981397] fgetty[1322] vsyscall attempted with vsyscall=none ip:ffffffffff600400 cs:33 sp:7fffa6d94100 ax:ff[   15.004560] fgetty[1322]: segfault at ffffffffff600400 ip ffffffffff600400 sp 00007fffa6d94100 error 15
 INIT: Id "2" respawning too fast: disabled for 5 minutes

3:23:respawn:/sbin/ngetty 3
# Produces error. Output:
 [   14.670134] ngetty-helper[1311] vsyscall attempted with vsyscall=none ip:ffffffffff600400 cs:33 sp:7ffca011e1a[   14.684298] ngetty-helper[1311]: segfault at ffffffffff600400 ip ffffffffff600400 sp 00007ffca011e1a0 error 15


Please let me know if you consider these errors should be reported to fgetty and ngetty maintainers.

Kind regards,

Ricardo

[toc] | [next] | [standalone]

#56066

FromBen Hutchings <ben@decadent.org.uk>
Date2016-12-09 14:10 +0100
Message-ID<sMt61-3Ds-17@gated-at.bofh.it>
In reply to#56060

[Multipart message — attachments visible in raw view] — view raw

On Fri, 2016-12-09 at 01:18 -0300, Ricardo Fabian Peliquero wrote:
> Dear Maintainer,
> 
> After upgrading
> 
>  from: linux-image-4.8.0-1-amd64-unsigned:amd64 (4.8.5-1)
>    to: linux-image-4.9.0-rc8-amd64-unsigned:amd64 (4.9~rc8-1~exp1)
> 
> and installing mingetty(8)
> 
> the system is booting well (e.g. without kernel panic).
> 
> But the following errors appeared for ttys using these lines in /etc/inittab:
> 
> 2:23:respawn:/sbin/fgetty tty2
> # Produces error. Output:
>  [   14.741345] fgetty[1309] vsyscall attempted with vsyscall=none ip:ffffffffff600400 cs:33 sp:7ffcb7dbade0 ax:ff[   14.753469] fgetty[1309]: segfault at ffffffffff600400 ip ffffffffff600400 sp 00007ffcb7dbade0 error 15
>  [   14.761442] fgetty[1314] vsyscall attempted with vsyscall=none ip:ffffffffff600400 cs:33 sp:7ffc57494eb0 ax:ff[   14.774655] fgetty[1314]: segfault at ffffffffff600400 ip ffffffffff600400 sp 00007ffc57494eb0 error 15
>  [   14.783045] fgetty[1315] vsyscall attempted with vsyscall=none ip:ffffffffff600400 cs:33 sp:7fff4cd23c40 ax:ff[   14.797132] fgetty[1315]: segfault at ffffffffff600400 ip ffffffffff600400 sp 00007fff4cd23c40 error 15
>  [   14.805678] fgetty[1316] vsyscall attempted with vsyscall=none ip:ffffffffff600400 cs:33 sp:7ffebc275580 ax:ff[   14.820255] fgetty[1316]: segfault at ffffffffff600400 ip ffffffffff600400 sp 00007ffebc275580 error 15
>  [   14.829085] fgetty[1317] vsyscall attempted with vsyscall=none ip:ffffffffff600400 cs:33 sp:7ffdf2ba87d0 ax:ff[   14.846203] fgetty[1317]: segfault at ffffffffff600400 ip ffffffffff600400 sp 00007ffdf2ba87d0 error 15
>  [   14.855785] fgetty[1318] vsyscall attempted with vsyscall=none ip:ffffffffff600400 cs:33 sp:7fff05d8bca0 ax:ff[   14.873951] fgetty[1318]: segfault at ffffffffff600400 ip ffffffffff600400 sp 00007fff05d8bca0 error 15
>  [   14.883984] fgetty[1319] vsyscall attempted with vsyscall=none ip:ffffffffff600400 cs:33 sp:7ffdb25fe940 ax:ff[   14.903582] fgetty[1319]: segfault at ffffffffff600400 ip ffffffffff600400 sp 00007ffdb25fe940 error 15
>  [   14.914209] fgetty[1320] vsyscall attempted with vsyscall=none ip:ffffffffff600400 cs:33 sp:7ffe39d6bda0 ax:ff[   14.934960] fgetty[1320]: segfault at ffffffffff600400 ip ffffffffff600400 sp 00007ffe39d6bda0 error 15
>  [   14.946825] fgetty[1321] vsyscall attempted with vsyscall=none ip:ffffffffff600400 cs:33 sp:7fff000656c0 ax:ff[   14.968608] fgetty[1321]: segfault at ffffffffff600400 ip ffffffffff600400 sp 00007fff000656c0 error 15
>  [   14.981397] fgetty[1322] vsyscall attempted with vsyscall=none ip:ffffffffff600400 cs:33 sp:7fffa6d94100 ax:ff[   15.004560] fgetty[1322]: segfault at ffffffffff600400 ip ffffffffff600400 sp 00007fffa6d94100 error 15
>  INIT: Id "2" respawning too fast: disabled for 5 minutes
> 
> 3:23:respawn:/sbin/ngetty 3
> # Produces error. Output:
>  [   14.670134] ngetty-helper[1311] vsyscall attempted with vsyscall=none ip:ffffffffff600400 cs:33 sp:7ffca011e1a[   14.684298] ngetty-helper[1311]: segfault at ffffffffff600400 ip ffffffffff600400 sp 00007ffca011e1a0 error 15
> 
> 
> Please let me know if you consider these errors should be reported to fgetty and ngetty maintainers.

fgetty uses dietlibc, and the stable version of dietlibc still uses the
vsyscall feature which is now disabled by default.  You can make it
work again by adding 'vsyscall=emulate' to the kernel command line.

I'll have to reconsider whether to revert the configuration change now
that I know dietlibc is a problem.

Ben.

-- 
Ben Hutchings
Logic doesn't apply to the real world. - Marvin Minsky

[toc] | [prev] | [next] | [standalone]

#56073

FromRicardo Fabian Peliquero <zhana@lasampa.com.ar>
Date2016-12-09 17:40 +0100
Message-ID<sMwnf-5zi-11@gated-at.bofh.it>
In reply to#56066
On Fri, Dec 09, 2016 at 01:03:44PM +0000, Ben Hutchings wrote:
> On Fri, 2016-12-09 at 01:18 -0300, Ricardo Fabian Peliquero wrote:
> >  from: linux-image-4.8.0-1-amd64-unsigned:amd64 (4.8.5-1)
> >    to: linux-image-4.9.0-rc8-amd64-unsigned:amd64 (4.9~rc8-1~exp1)
> > and installing mingetty(8)
> > the system is booting well (e.g. without kernel panic).
> > 
> > But the following errors appeared for ttys using these lines in /etc/inittab:
> > 
> > 2:23:respawn:/sbin/fgetty tty2
> > # Produces error. Output:
> >  [   14.741345] fgetty[1309] vsyscall attempted with vsyscall=none ip:ffffffffff600400 cs:33 sp:7ffcb7dbade0 ax:ff[   14.753469] fgetty[1309]: segfault at ffffffffff600400 ip ffffffffff600400 sp 00007ffcb7dbade0 error 15
> > ...
> >  INIT: Id "2" respawning too fast: disabled for 5 minutes
> > 
> > 3:23:respawn:/sbin/ngetty 3
> > # Produces error. Output:
> >  [   14.670134] ngetty-helper[1311] vsyscall attempted with vsyscall=none ip:ffffffffff600400 cs:33 sp:7ffca011e1a[   14.684298] ngetty-helper[1311]: segfault at ffffffffff600400 ip ffffffffff600400 sp 00007ffca011e1a0 error 15
> 
> fgetty uses dietlibc, and the stable version of dietlibc still uses the
> vsyscall feature which is now disabled by default.  You can make it
> work again by adding 'vsyscall=emulate' to the kernel command line.
> 
> I'll have to reconsider whether to revert the configuration change now
> that I know dietlibc is a problem.

Your suggestion worked here.

I will be using vsyscall emulation option appended to lilo.conf until better resolution.

Thank you!

Ricardo

[toc] | [prev] | [next] | [standalone]

#56293

FromDidier 'OdyX' Raboud <odyx@debian.org>
Date2016-12-19 12:20 +0100
Message-ID<sQ493-70A-7@gated-at.bofh.it>
In reply to#56066

[Multipart message — attachments visible in raw view] — view raw

Control: found -1 4.8.11-1

Le vendredi, 9 décembre 2016, 13.03:44 h CET Ben Hutchings a écrit :
> fgetty uses dietlibc, and the stable version of dietlibc still uses the
> vsyscall feature which is now disabled by default.  You can make it
> work again by adding 'vsyscall=emulate' to the kernel command line.
> 
> I'll have to reconsider whether to revert the configuration change now
> that I know dietlibc is a problem.

On a vagrant-lxc setup using Liip's drifter [0], we see two different programs 
segfaulting immediately after a vsyscall entry in syslog:

Dec 19 10:07:55 gyllingar kernel: [  834.998381] logsave[12259] vsyscall 
attempted with vsyscall=none ip:ffffffffff600400 cs:33 sp:7ffc918c1fc8 
ax:ffffffffff600400 si:4017c1 di:0
Dec 19 10:07:55 gyllingar kernel: [  834.998384] logsave[12259]: segfault at 
ffffffffff600400 ip ffffffffff600400 sp 00007ffc918c1fc8 error 15
Dec 19 10:07:55 gyllingar kernel: [  834.998934] ip[12261] vsyscall attempted 
with vsyscall=none ip:ffffffffff600400 cs:33 sp:7fff467d8d18 
ax:ffffffffff600400 si:433d2f di:0
Dec 19 10:07:55 gyllingar kernel: [  834.998936] ip[12261]: segfault at 
ffffffffff600400 ip ffffffffff600400 sp 00007fff467d8d18 error 15

So apparently /sbin/logsave from src:e2fsprogs and /sbin/ip from src:iproute2 
have the same problem. And this was on linux-image-4.8.0-2-amd64 4.8.11-1.

Both problems are circumvented by booting with vsyscall=emulated on the kernel 
command line.

Cheers,
OdyX

[0] https://github.com/liip/drifter

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web