linux-kernel - Re: [PATCH v2] selftests/cgroup: memory controller self-tests

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: <20180511162920.GV2368884@devbig577.frc2.facebook.com>
Date:   Fri, 11 May 2018 09:29:20 -0700
From:   Tejun Heo <tj@...nel.org>
To:     Shuah Khan <shuah@...nel.org>
Cc:     Roman Gushchin <guro@...com>, Johannes Weiner <hannes@...xchg.org>,
        Michal Hocko <mhocko@...e.com>,
        Mike Rapoport <rppt@...ux.vnet.ibm.com>, kernel-team@...com,
        linux-kselftest@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] selftests/cgroup: memory controller self-tests

Hello, Shuah.

On Fri, May 11, 2018 at 08:55:28AM -0600, Shuah Khan wrote:
> I think we don't need to create a special branch and all. The following
> should work:
> 
> linux-next already has the skip work. What we can do is:
> 
> Do the cleanup and test it against linux-next. In linux-next SKIP isn't PASS. If test is
> compiled on linux-next, you will see that SKIP is SKIP. If it is compiled on the mainline,
> it will be reported PASS, which will be a temporary state.

Hah, why not just create a branch and make sure what we see in the
topic branch is what we'll push?  That's how these things are done
usually.

Thanks.

-- 
tejun