Re: [PATCH nft 0/3] tests/shell: minor improvements to "run-tests.sh"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 2023-09-27 at 22:27 +0200, Pablo Neira Ayuso wrote:
> Hi Thomas,
> 
> Not precisely related to this series in this email thread, but...
> 
> I occasionally see errors like this when running tests in a loop:
> 
> ./run-tests.sh: line 673: echo: write error: Interrupted system call
> 
> it is happening since the recent updates, do you have any idea what
> could be wrong?
> 
> Thanks.
> 

Hi,


I think that line is

»·······echo scan > /sys/kernel/debug/kmemleak

Are you running with KMEMLEAK=y? But also without that, it gets called
after every 30th test returning -- since usually the fast tests run
quickly in parallel, we would call it more frequently at the beginning
of the tests.


Note that the "check_kmemleak_force" function in the run-tests.sh
script does NOT run in parallel. 


I am not familiar with kmemleak, but seems not serious. 
Maybe just ignore the error output?

  ( echo scan > /sys/kernel/debug/kmemleak ) &>/dev/null


Thomas





[Index of Archives]     [Netfitler Users]     [Berkeley Packet Filter]     [LARTC]     [Bugtraq]     [Yosemite Forum]

  Powered by Linux