mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] x86/urgent for 6.1-rc6
Date: Sun, 20 Nov 2022 13:16:35 +0100	[thread overview]
Message-ID: <Y3oao37SUu9tluFY@zn.tnic> (raw)

Hi Linus,

please pull two urgent x86 fixes for 6.1.

Thx.

---

The following changes since commit f0c4d9fc9cc9462659728d168387191387e903cc:

  Linux 6.1-rc4 (2022-11-06 15:07:11 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/x86_urgent_for_v6.1_rc6

for you to fetch changes up to 36b038791e1e2baea892e9276588815fd14894b4:

  x86/fpu: Drop fpregs lock before inheriting FPU permissions (2022-11-10 16:57:38 +0100)

----------------------------------------------------------------
- Do not hold fpregs lock when inheriting FPU permissions because the
fpregs lock disables preemption on RT but fpu_inherit_perms() does
spin_lock_irq(), which, on RT, uses rtmutexes and they need to be
preemptible.

- Check the page offset and the length of the data supplied by userspace
for overflow when specifying a set of pages to add to an SGX enclave

----------------------------------------------------------------
Borys Popławski (1):
      x86/sgx: Add overflow check in sgx_validate_offset_length()

Mel Gorman (1):
      x86/fpu: Drop fpregs lock before inheriting FPU permissions

 arch/x86/kernel/cpu/sgx/ioctl.c | 3 +++
 arch/x86/kernel/fpu/core.c      | 2 +-
 2 files changed, 4 insertions(+), 1 deletion(-)

-- 
Regards/Gruss,
    Boris.

SUSE Software Solutions Germany GmbH
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Martje Boudien Moerman
(HRB 36809, AG Nürnberg)

             reply	other threads:[~2022-11-20 12:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-20 12:16 Borislav Petkov [this message]
2022-11-20 18:52 ` pr-tracker-bot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Y3oao37SUu9tluFY@zn.tnic \
    --to=bp@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®