1445907560 Q * fstd Remote host closed the connection
1445907573 J * fstd ~fstd@xdsl-81-173-187-9.netcologne.de
1445927267 N * Bertl_zZ Bertl
1445927268 M * Bertl morning folks!
1445930348 J * Ghislain ~aqueos@adsl1.aqueos.com
1445932513 Q * derjohn_mob Ping timeout: 480 seconds
1445936281 J * derjohn_mob ~aj@p4FFA5834.dip0.t-ipconnect.de
1445937072 Q * derjohn_mob Ping timeout: 480 seconds
1445938755 Q * eyck Quit: leaving
1445938837 J * eyck ~eyck@u28n61.nowanet.pl
1445938978 J * derjohn_mob ~aj@tmo-106-40.customers.d1-online.com
1445945917 Q * Aiken Ping timeout: 480 seconds
1445948278 Q * derjohn_mob Ping timeout: 480 seconds
1445950761 Q * fstd Remote host closed the connection
1445950772 J * fstd ~fstd@xdsl-87-78-19-140.netcologne.de
1445961268 M * Bertl off for now ... bbl
1445961271 N * Bertl Bertl_oO
1445965966 Q * fstd Remote host closed the connection
1445966087 J * fstd ~fstd@xdsl-87-78-19-140.netcologne.de
1445968327 J * derjohn_mob ~aj@88.128.80.167
1445970785 M * Ghislain quick question, i see in /proc/virtual/xx/limit : DENT:   692194974 
1445970806 M * Ghislain what happen if i go +1 of the max counter value ?
1445971021 M * Ghislain and generaly to any counter inside the vserver limit system
1445971354 M * Ghislain not sure to grasp the dentry thing, it should not be more dentry than files+directory+sockets it seems
1445971522 M * Ghislain on a very busy non vserver i got 4586404 dentry, the dentry line in the guest is 692194974, another 390141624. perhaps they do not represrent the same thing
1445971613 M * Ghislain or there is a leek therefor the counter reach 32bit then perhaps it do nothing, perhaps this could explain my dentry crash issue
1445972146 M * daniel_hozac maybe.
1445975427 J * Aiken ~Aiken@quarry.jbmb.net
1445976484 J * sannes ~ace@2a02:fe0:c120:9660:2870:ee9:beb8:be24
1445979069 Q * derjohn_mob Remote host closed the connection
1445979142 J * derjohn_mob ~aj@88.128.80.167
1445980341 M * daniel_hozac doesn't look like it should matter though.
1445980349 M * daniel_hozac assuming you don't actually put limits on it.
1445982199 Q * derjohn_mob Ping timeout: 480 seconds
1445985892 J * derjohn_mob ~aj@4Z9AAAGSS.tor-irc.dnsbl.oftc.net
1445985985 M * Ghislain if you increment the counter even if no limits are set the counter can overfloxw no ?
1445986216 M * Ghislain do the numbers shown seems right ? do the DENTRY should be the dentry used bu the guest then less than the first in /proc/sys/fs/dentry-state ?
1445987627 M * Bertl_oO off to bed now ... have a good one everyone
1445987629 N * Bertl_oO Bertl_zZ
1445987738 M * Ghislain i see a vx_dentry_inc(dentry); in  d_lookup, the counter is the lookup number or the actual number of dentry ?
1445987841 M * Ghislain vx_dentry_dec(dentry); is used in several place but not in v_drop, as invalidate and other call v_drop perhaps it would be a better place to put it unless there is a locking requirement
1445987999 M * Ghislain in this case i would move the decrease to be just before the unlock as for exemple in the d_invalidate the  vx_dentry_dec is before a if block that can return -EBUSY thereofr the decrease is done but the dentry not removed
1445988040 M * Ghislain i mus t go, i know i really badly read C just trying to understand
1445988128 Q * Ghislain Quit: Leaving.