linux-kernel - Re: [GIT PULL] UML fixes for 4.4-rc5

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: <CA+55aFx53MbO2HrVkrMr4K-8DU2gJTsmpaEECT3i4prUjcMUng@mail.gmail.com>
Date:	Tue, 8 Dec 2015 17:35:28 -0800
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Richard Weinberger <richard@....at>, Ingo Molnar <mingo@...nel.org>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	user-mode-linux-devel <user-mode-linux-devel@...ts.sourceforge.net>,
	"the arch/x86 maintainers" <x86@...nel.org>
Subject: Re: [GIT PULL] UML fixes for 4.4-rc5

On Tue, Dec 8, 2015 at 1:39 PM, Richard Weinberger <richard@....at> wrote:
>
> This pull request contains various bug fixes, most of them are
> fall out from the merge window.
>
> Richard Weinberger (2):
>       um: Fix fpstate handling

Ugh. This is very ugly. It's apparently the result of commit
530e5c827182 ("x86/headers: Make sigcontext pointers bit independent")
and apparently nobody noticed the uml fallout.

I've pulled, but I wanted the x86 people involved to be aware of this
ugly corner. I wonder if there might be some way for uml to continue
to use that fpstate entry as a pointer, at least when the wordsize
matches (which it will)?

                   Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/