1515112157 J * fstd_ ~fstd@xdsl-78-35-189-161.netcologne.de
1515112608 Q * fstd Ping timeout: 480 seconds
1515112608 N * fstd_ fstd
1515116012 Q * Aiken Remote host closed the connection
1515116170 J * Aiken ~Aiken@2001:44b8:2168:1000:b26e:bfff:fe2a:b951
1515120372 J * derjohn_mob_sisu ~aj@p2003008E6C0EAF00780F16701C7F58C7.dip0.t-ipconnect.de
1515120752 Q * derjohn_mob Ping timeout: 480 seconds
1515132085 N * Bertl_oO Bertl_zZ
1515139677 Q * derjohn_mob_sisu Quit: Leaving
1515141066 J * nikolay ~nikolay@149.235.255.3
1515142874 M * Ghislain1 hi folks, Bertl_zZ, daniel_hozac, i sent to the mailing list my test for the dir_emit thing and a possible solution that really need scrutiny to see if thisis right ;p
1515143585 M * arekm "4.14+ is in the works", wow, nice
1515143712 M * Le_Coyote Bertl_zZ: As I said in my email, the problem is the __contructor__ declaration. It works fine without it, so I'm not sure why it's there in the first place
1515150461 M * Ghislain1 ok my patch is wrong, when i do a find in /proc it does an infinite loop
1515154232 J * Gremble ~Gremble@cpc1-aztw34-2-0-cust397.18-1.cable.virginm.net
1515157386 Q * padde Remote host closed the connection
1515157484 J * padde ~padde@patrick-nagel.net
1515157963 Q * AlexanderS Quit: WeeChat 1.9.1
1515158095 J * AlexanderS ~Alexander@home.zedat.fu-berlin.de
1515162101 N * Bertl_zZ Bertl
1515162112 M * Bertl  morning folks!
1515162143 M * Bertl Le_Coyote: so _any_ __contructor__ declaration is bad for the hardened chain?
1515162681 Q * Gremble Quit: Leaving
1515165837 Q * nikolay Quit: Leaving
1515168171 M * Le_Coyote Bertl: apparently
1515168189 M * Le_Coyote Stack smash protector, specifically
1515168432 M * Le_Coyote I read something about this having to do with inline functions, but that's way over my head
1515168447 M * Le_Coyote All I know is that if I comment out these declarations, the binary runs fine
1515173528 J * tnpizza ~hhariyp@165.16.66.166
1515173529 Q * tnpizza Remote host closed the connection
1515174156 Q * dustinm` Quit: Leaving
1515174624 J * dustinm` ~dustinm`@68.ip-149-56-14.net
1515176434 J * obeardly ~obeardly@12.153.3.34
1515176515 Q * obeardly 
1515176521 J * obeardly ~obeardly@12.153.3.34
1515182574 M * jrayhawk Is the plan for meltdown to wait for a backport of KPTI to 4.1-stable, or is 4.14 experimental vserver support likely to be released soon?
1515187916 M * Bertl both
1515195750 N * Bertl Bertl_oO