linux-kernel - Re: [PATCH linux-next] sysctl: fix build error

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

Message-Id: <20190612171652.b8ba1f05d835e3fc870829e4@linux-foundation.org>
Date:   Wed, 12 Jun 2019 17:16:52 -0700
From:   Andrew Morton <akpm@...ux-foundation.org>
To:     Matteo Croce <mcroce@...hat.com>
Cc:     linux-next@...r.kernel.org, Song Liu <songliubraving@...com>,
        linux-kernel@...r.kernel.org, Johannes Weiner <hannes@...xchg.org>,
        Aaron Tomlin <atomlin@...hat.com>
Subject: Re: [PATCH linux-next] sysctl: fix build error

On Thu, 13 Jun 2019 00:01:20 +0200 Matteo Croce <mcroce@...hat.com> wrote:

> Commit cefdca0a86be ("userfaultfd/sysctl: add vm.unprivileged_userfaultfd")
> reintroduces a reference to 'zero' and 'one'.
> Use the SYSCTL_{ZERO,ONE} symbols instead.

proc-sysctl-add-shared-variables-for-range-check-fix.patch (which has
been in linux-next for over a week) already fixed that.

> Reported-by: kbuild test robot <lkp@...el.com>

Some robot glitch I guess?