linux-kernel - Re: [PATCH 4.17 00/70] 4.17.3-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]

Message-ID: <20180625065557.GA5140@kroah.com>
Date:   Mon, 25 Jun 2018 14:55:57 +0800
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Naresh Kamboju <naresh.kamboju@...aro.org>
Cc:     open list <linux-kernel@...r.kernel.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Guenter Roeck <linux@...ck-us.net>,
        Shuah Khan <shuah@...nel.org>, patches@...nelci.org,
        Ben Hutchings <ben.hutchings@...ethink.co.uk>,
        lkft-triage@...ts.linaro.org,
        linux- stable <stable@...r.kernel.org>
Subject: Re: [PATCH 4.17 00/70] 4.17.3-stable review

On Mon, Jun 25, 2018 at 12:10:08PM +0530, Naresh Kamboju wrote:
> On 24 June 2018 at 20:51, Greg Kroah-Hartman <gregkh@...uxfoundation.org> wrote:
> > This is the start of the stable review cycle for the 4.17.3 release.
> > There are 70 patches in this series, all will be posted as a response
> > to this one.  If anyone has any issues with these being applied, please
> > let me know.
> >
> > Responses should be made by Tue Jun 26 14:27:20 UTC 2018.
> > Anything received after that time might be too late.
> >
> > The whole patch series can be found in one patch at:
> >         https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.17.3-rc1.gz
> > or in the git tree and branch at:
> >         git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.17.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
> 
> Results from Linaro’s test farm.
> No regressions on arm64 and arm.
> 
> Kselftest test case mov_ss_trap_64 is causing kernel panic on
> qemu-system-x86_64 and PASS on real x86_64 hardware.
> 
> [RUN] MOV SS; CSx14 INT3
> [  762.263790] PANIC: double fault, error_code: 0x0
> [  762.265169] CPU: 2 PID: 3380 Comm: mov_ss_trap_64 Not tainted 4.17.3-rc1 #1
> [  762.267588] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996),
> BIOS 1.10.2-1 04/01/2014
> [  762.273190] RIP: 0010:error_entry+0x12/0x100
> 
> Test code snippet,
> main() {
> <>
>     printf("[RUN]\tMOV SS; CS CS INT3\n");
>     asm volatile ("mov %[ss], %%ss; .byte 0x2e, 0x2e; int3" :: [ss] "m" (ss));
> <>
> }
> 
> Reported upstream,
> https://lkml.org/lkml/2018/6/25/19

Nit, there is a better way to refer to lkml emails, see the bottom of
this page as lots of time lkml.org does not work for people:
	https://www.kernel.org/lore.html

This looks like a quemu bug, not a kernel issue, so did you tell the
qemu developers about this?

In looking at the full headers:
	https://lore.kernel.org/lkml/CA+G9fYu0E0fM+WaFim1WKup5BZvjtGZ_4ii5FhTUjNZEqaAuwA@mail.gmail.com/
it doesn't look like you did :(

thanks,

greg k-h