linux-kernel - Re: [PATCH 4.9 00/86] 4.9.88-stable review

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]

Date:   Wed, 21 Mar 2018 14:32:56 +0100
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Ben Hutchings <ben.hutchings@...ethink.co.uk>
Cc:     Naresh Kamboju <naresh.kamboju@...aro.org>,
        open list <linux-kernel@...r.kernel.org>,
        Shuah Khan <shuahkh@....samsung.com>,
        lkft-triage@...ts.linaro.org, patches@...nelci.org,
        linux- stable <stable@...r.kernel.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Guenter Roeck <linux@...ck-us.net>
Subject: Re: [PATCH 4.9 00/86] 4.9.88-stable review

On Tue, Mar 20, 2018 at 11:49:19PM +0000, Ben Hutchings wrote:
> On Sun, 2018-03-18 at 11:27 +0100, Greg Kroah-Hartman wrote:
> > On Sat, Mar 17, 2018 at 03:48:24PM +0530, Naresh Kamboju wrote:
> [...]
> > > Results from Linaro’s test farm.
> > > No regressions on arm64, arm, qemu_x86_64 and x86_64.
> > > 
> > > NOTE:
> > > CONFIG_LEGACY_VSYSCALL_EMULATE=y is enabled from config as default.
> > > Enabled vsyscall=native and vsyscall=none from kernel command line for testing
> > > selftests/x86/test_vsyscall test case on x86_64 and qemu_x86_64.
> > > 
> > > test_vdso_64 failed on x86_64 device when vsyscall=none is enabled.
> > > We will investigate this new test failure.
> > 
> > I think vsyscall=none just went away :)
> 
> No, vsyscall=native went away upstream.  vsyscall=none should still
> work everywhere.

Ah, sorry, got that wrong, thanks for the correction.

> However, test_vdso_64 isn't able to detect what the current
> configuration is and it will crash with vsyscall=none (or the
> equivalent default in kconfig).

That's good to know.  Naresh, does that help out?

thanks,

greg k-h