linux-kernel - [GIT PULL] x86/fpu updates

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

Date:	Mon, 2 Mar 2015 21:13:59 +0100
From:	Borislav Petkov <bp@...en8.de>
To:	x86-ml <x86@...nel.org>
Cc:	lkml <linux-kernel@...r.kernel.org>
Subject: [GIT PULL] x86/fpu updates

Hi guys,

those three are ontop of current tip/x86/fpu; please pull,

thanks.

The following changes since commit f353e612304ba752d6b613dc02eae8116cd3e27b:

  Merge branch 'tip-x86-fpu' of git://git.kernel.org/pub/scm/linux/kernel/git/bp/bp into x86/fpu (2015-02-19 11:19:05 +0100)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/bp/bp.git tags/tip_x86_fpu

for you to fetch changes up to 110d7f7513bbb916b8654da9e2973ac5bed929a9:

  x86/fpu: Don't abuse FPU in kernel threads if use_eager_fpu() (2015-02-23 15:50:45 +0100)

----------------------------------------------------------------
Three more cleanups/improvements to the FPU handling code. (Oleg Nesterov)

----------------------------------------------------------------
Oleg Nesterov (3):
      x86/fpu: __kernel_fpu_begin() should clear fpu_owner_task even if use_eager_fpu()
      x86/fpu: Always allow FPU in interrupt if use_eager_fpu()
      x86/fpu: Don't abuse FPU in kernel threads if use_eager_fpu()

 arch/x86/kernel/i387.c    | 11 ++++++-----
 arch/x86/kernel/process.c |  7 +++++++
 arch/x86/kernel/xsave.c   | 13 +------------
 3 files changed, 14 insertions(+), 17 deletions(-)

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--
--
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/