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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20150901233557.GB21660@fifo99.com>
Date:	Tue, 1 Sep 2015 16:35:57 -0700
From:	dwalker@...o99.com
To:	rostedt@...dmis.org
Cc:	linux-kernel@...r.kernel.org
Subject: ktest reboot on each test


Steven,

I was playing with ktest.pl and I found that it reboots after each test. What I wanted to do was to boot
the system with one TEST_START section, then leave it booted. I would have additional TEST_START sections
which would run on the already booted target. The only way I see to do that is to override the reboot and
powercycling options so that when it attempts to reboot it's just a nop. Is that the only way to do this
or is there something I'm missing ?

I also have these set,

REBOOT_ON_SUCCESS = 0
REBOOT_ON_ERROR = 0
POWEROFF_ON_ERROR = 0
POWEROFF_ON_SUCCESS = 0

but every TEST_START seems to reboot regardless. It seems to be in the sub monitor , it calls reboot_to()
which ends up rebooting.

Any help appreciated.

Daniel
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ