| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20130902133923.GA2368@swordfish.minsk.epam.com> Date: Mon, 2 Sep 2013 16:39:23 +0300 From: Sergey Senozhatsky <sergey.senozhatsky@...il.com> To: Frederic Weisbecker <fweisbec@...il.com> Cc: Stanislaw Gruszka <sgruszka@...hat.com>, Ingo Molnar <mingo@...hat.com>, Peter Zijlstra <peterz@...radead.org>, "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>, Borislav Petkov <bp@...en8.de>, linux-kernel@...r.kernel.org Subject: Re: [sched next] overflowed cpu time for kernel threads in /proc/PID/stat On (09/02/13 15:07), Frederic Weisbecker wrote: > > $ dmesg | grep Ooops > > [ 1295.311056] Ooops: stime:4622750929 rtime:4622750928 > > [ 1301.384396] Ooops: stime:4654072951 rtime:4654072950 > > [ 1307.438935] Ooops: stime:4687858107 rtime:4687858106 > > [ 1313.493462] Ooops: stime:4724166945 rtime:4724166944 > > [ 1316.521740] Ooops: stime:4741142233 rtime:4741142232 > > [ 1325.605625] Ooops: stime:4793906690 rtime:4793906688 > > [ 1331.648611] Ooops: stime:4308413629 rtime:4308413628 > > [ 1337.708468] Ooops: stime:4510156747 rtime:4510156746 > > [ 1340.744586] Ooops: stime:4880584390 rtime:4880584389 > > [ 1343.773111] Ooops: stime:4442005879 rtime:4442005878 > > [ 1343.773362] Ooops: stime:4558310943 rtime:4558310942 > > [ 1349.815797] Ooops: stime:4927379646 rtime:4927379645 > > [ 1352.836936] Ooops: stime:4942782836 rtime:4942782834 > > [ 1358.885232] Ooops: stime:4979031940 rtime:4979031938 > > [ 1364.977902] Ooops: stime:5019633914 rtime:5019633912 > > [ 1364.978283] Ooops: stime:4601969101 rtime:4601969100 > > [ 1364.978623] Ooops: stime:4826393815 rtime:4826393814 > > [ 1371.034265] Ooops: stime:4894272175 rtime:4894272174 > > [ 1374.077150] Ooops: stime:4688831829 rtime:4688831828 > > [ 1374.077519] Ooops: stime:4916319315 rtime:4916319314 > > [ 1377.110416] Ooops: stime:5084174048 rtime:5084174047 > > [ 1377.111043] Ooops: stime:4949250198 rtime:4949250196 > > [ 1380.137382] Ooops: stime:5096963048 rtime:5096963046 > > [ 1380.137739] Ooops: stime:4975014880 rtime:4975014879 > > [ 1383.161441] Ooops: stime:5002466396 rtime:5002466394 > > [ 1389.212166] Ooops: stime:5140400038 rtime:5140400036 > > [ 1392.239303] Ooops: stime:5082051028 rtime:5082051027 > > [ 1395.270391] Ooops: stime:5170118636 rtime:5170118634 > > [ 1398.303593] Ooops: stime:5184355318 rtime:5184355316 > > > Thanks a lot Sergey for testing this further! > > Interesting results, so rtime is always one or two units off stime after scaling. > Stanislaw made the scaling code with Linus and he has a better idea on the math guts > here. > > Stanislaw, any idea? sure. sorry, it took so long to get back to this. actual scale_stime() input that triggers overflow: [ 1291.409566] stime:3790580815 rtime:4344293130 total:3790580815 [ 1300.484675] stime:3966526699 rtime:4316110636 total:3966526699 [ 1309.548850] stime:4016453845 rtime:4369061182 total:4016453845 [ 1315.597880] stime:4055256777 rtime:4409603756 total:4055256777 [ 1315.598340] stime:4004230541 rtime:4571167362 total:4004230541 [ 1318.623774] stime:4072651687 rtime:4427641260 total:4072651687 [ 1318.624194] stime:3307672697 rtime:4359433252 total:3307672697 [ 1321.661950] stime:4073588267 rtime:4644946914 total:4073588267 [ 1324.691457] stime:4105876887 rtime:4462631018 total:4105876887 [ 1327.722074] stime:3375231967 rtime:4439900096 total:3375231967 [ 1333.757482] stime:4156087279 rtime:4514990216 total:4156087279 [ 1333.757755] stime:3427423145 rtime:4504337498 total:3427423145 [ 1333.758080] stime:4180115893 rtime:4758073724 total:4180115893 [ 1339.813117] stime:3465843945 rtime:4554325330 total:3465843945 [ 1342.845746] stime:4204665773 rtime:4565346324 total:4204665773 [ 1345.888570] stime:3497346343 rtime:4592210094 total:3497346343 [ 1348.922371] stime:4348957782 rtime:4935439460 total:4348957782 [ 1351.950096] stime:4362056506 rtime:4949617939 total:4362056506 [ 1361.021453] stime:4295785738 rtime:4661661137 total:4295785738 [ 1361.022000] stime:4458897246 rtime:5051395981 total:4458897246 [ 1364.050371] stime:4311972683 rtime:4678581654 total:4311972683 [ 1364.050765] stime:4479087426 rtime:5072949454 total:4479087426 [ 1367.076973] stime:4499465526 rtime:5094687861 total:4499465526 [ 1370.099987] stime:4343775870 rtime:4712036053 total:4343775870 [ 1373.125650] stime:4359154163 rtime:4727095545 total:4359154163 [ 1373.126009] stime:4552630150 rtime:5150626456 total:4552630150 [ 1376.148541] stime:4374640011 rtime:4743265121 total:4374640011 [ 1379.177031] stime:3732027459 rtime:4887067184 total:3732027459 [ 1382.220666] stime:4404735122 rtime:4774829507 total:4404735122 [ 1385.246696] stime:4420289930 rtime:4790957716 total:4420289930 [ 1385.247197] stime:4649961982 rtime:5253432805 total:4649961982 [ 1388.269661] stime:4433706951 rtime:4804365472 total:4433706951 [ 1388.270078] stime:3783514895 rtime:4952742424 total:3783514895 [ 1391.299533] stime:4449952651 rtime:4821791998 total:4449952651 [ 1394.329016] stime:4463714342 rtime:4836891922 total:4463714342 -ss -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists