1582517351 Q * transacid Remote host closed the connection
1582517373 J * transacid ~transacid@transacid.de
1582524390 J * Ghislain ~Ghislain@adsl2.aqueos.com
1582525552 M * Bertl_oO  off to bed now ... have a good one everyone!
1582525554 N * Bertl_oO Bertl_zZ
1582531154 J * hijacker ~nikolay@2001:981:4551:1:4ce2:2999:7769:a684
1582532502 Q * hijacker 
1582536256 J * hijacker ~nikolay@149.235.255.3
1582539331 M * Guy- Bertl_zZ: hi, on 4.9.207-vs2.3.9.9, I was able to produce a kernel null pointer dereference by using chcontext --xid 1 -- strace from the 64bit host on a number of 32bit guest processes simultaneously
1582540487 Q * hijacker Ping timeout: 480 seconds
1582542774 J * hijacker ~nikolay@213.161.83.122
1582545854 Q * Aiken Remote host closed the connection
1582556066 M * Guy- there is a nontrivial conflict in meminfo_proc_show with 4.4.214 and http://vserver.13thfloor.at/Experimental/patch-4.4.195-vs2.3.9.8.diff
1582556178 M * Guy- the code to be modified moved to si_mem_available() in mm/page_alloc.c
1582557691 M * Guy- also:
1582557692 M * Guy- # cat /proc/1/sched
1582557692 M * Guy- runit (17472, #threads: 1)
1582557717 M * Guy- this is arguably an information leak; otoh, it's handy for detecting that you're running inside a container
1582558416 M * AlexanderS Guy-: You can already check, if you are inside a container with something like this: grep VxID /proc/self/status
1582558758 M * Guy- AlexanderS: yes but that only works for vserver
1582558784 M * Guy- looking at /proc/1/sched also works for lxc, likely docker
1582558815 M * Guy- (in lxc, the file is empty)
1582559040 M * AlexanderS I have an lxc guest with "systemd (1, #threads: 1)" in this file. So this likely depends on the setup.
1582559129 M * Guy- AlexanderS: maybe your guest has the host's real /proc?
1582559182 M * Guy- anyway, this /proc/1/sched hack is what eudev from Devuan now uses to avoid starting in a container
1582559236 M * Guy- I think it's wrong for them to try to avoid this (the user should have the option of shooting themselves in the foot), so I won't complain about setups where it fails to detect a container :)
1582559263 M * Guy- I had a problem with their previous approach that mis-detected my runit-using hosts as being containers
1582560496 N * Bertl_zZ Bertl
1582560498 M * Bertl  morning folks!
1582560527 M * Bertl Guy-: I'd be interested in the kernel stack trace of the null pointer dereference
1582560553 M * Bertl also, will look at the conflict a little later ...
1582564345 Q * hijacker 
1582569632 J * fstd_ ~fstd@xdsl-87-79-157-139.nc.de
1582570098 Q * fstd Ping timeout: 480 seconds
1582572457 J * Aiken ~Aiken@b951.h.jbmb.net
1582577123 Q * Guy- Quit: malenkiy reboot
1582579154 M * Bertl  off for now ... bbl
1582579155 N * Bertl Bertl_oO
1582579365 Q * Ghislain 
1582580963 J * Guy- ~korn@0002809d.user.oftc.net