[CRIU] Weird results in test

[Dmitry Safonov]

On 02/08/2016 02:49 PM, Dmitry Safonov wrote:
> On 02/08/2016 02:34 PM, Cyrill Gorcunov wrote:
>> Dima, I've tried today's repo of criu to run test on our PCS7
>> kernel, and got the following
>>
>> ==================== Run zdtm/live/static/fifo_wronly in h 
>> =====================
>> Start test
>> ./fifo_wronly --pidfile=fifo_wronly.pid --outfile=fifo_wronly.out 
>> --filename=fifo_wronly.test
>> Run criu dump
>> =[log]=> dump/zdtm/live/static/fifo_wronly/60/1/dump.log
>> ------------------------ grep Error ------------------------
>> (00.001985) Error (proc_parse.c:839): Can't open 62/loginuid on 
>> procfs: No such file or directory
>> ------------------------ ERROR OVER ------------------------
>> Run criu restore
>> =[log]=> dump/zdtm/live/static/fifo_wronly/60/1/restore.log
>> ------------------------ grep Error ------------------------
>> (00.001094) Error (proc_parse.c:839): Can't open 63/loginuid on 
>> procfs: No such file or directory
>> ------------------------ ERROR OVER ------------------------
>> Wait for zdtm/live/static/fifo_wronly to die for 0.100000
>> Removing dump/zdtm/live/static/fifo_wronly/60
>> ==================== Test zdtm/live/static/fifo_wronly PASS 
>> ====================
>>
>> Does loginuid requires some particular kernel CONFIG or anything else?
> Yes, files /proc/<pid>/loginuid are present only with 
> CONFIG_AUDITSYSCALL option.
> But, I added fetching of logiuid C/R feature in kerndat. (it outputs 
> as warning if
> one does not have this files or cannot read/write them)
> Your output is on feature testing, I will make a patch this to be 
> warning also.
> Thanks for the report.
So, everything fine with the test, just feature present testing fail 
reports on LOG_ERR
level instead of LOG_WARN with disabled CONFIG_AUDITSYSCALL.
>>
>>     Cyrill
>


-- 
Regards,
Dmitry Safonov