linux-kernel - Re: [PATCH 2/3] torture: Add --configonly parameter for kvm.sh

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20210517105545.GB199206@lothringen>
Date:   Mon, 17 May 2021 12:55:45 +0200
From:   Frederic Weisbecker <frederic@...nel.org>
To:     "Paul E. McKenney" <paulmck@...nel.org>
Cc:     LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/3] torture: Add --configonly parameter for kvm.sh

On Fri, May 07, 2021 at 01:29:10PM -0700, Paul E. McKenney wrote:
> On Thu, May 06, 2021 at 03:15:09PM +0200, Frederic Weisbecker wrote:
> > Those who just want the resulting config file to generate for bare metal
> > don't need to wait for the build. Provide an option to only produce
> > the .config file.
> > 
> > Signed-off-by: Frederic Weisbecker <frederic@...nel.org>
> 
> This one looks good to me, though it depends on 1/3.
> 
> I considered asking for a check of both --configonly and --buildonly,
> but on second thought I just couldn't see the point.  After all, it
> does say why it stopped, either "Config-only run" or "Build-only run"
> and that should suffice.

Ok, I'll resend this one as standalone then so we can think more clearly
on the rest.

Thanks!