From: Rik van Riel <riel@redhat.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Daniel J Blueman <daniel@quora.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH, 3.18] sleeping function called from invalid context
Date: Wed, 10 Dec 2014 20:32:34 -0500 [thread overview]
Message-ID: <5488F432.5010405@redhat.com> (raw)
In-Reply-To: <CALCETrVGH0VbGDWEx-D=gU7o3keM6PgGfYLixADH-sgNxhxJDA@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 12/10/2014 07:51 PM, Andy Lutomirski wrote:
> On Wed, Dec 10, 2014 at 4:49 PM, Rik van Riel <riel@redhat.com>
> wrote: On 12/10/2014 07:46 PM, Daniel J Blueman wrote:
>>>> Gah. I had some non-temporal copy changes in the wrong tree.
>>>> I'll check with a definitely clean tree and follow up if it
>>>> still occurs.
>
> The exception handlers should definitely allow sleeping, so I
> suspect those changes may be related.
>
>> It would be really, really nice if we could arrange for
>> kernel_fpu_begin to be unconditionally usable in anything except
>> NMI context. The crypto code would be much less scary, we could
>> make non-temporal copies safe, etc. Can we have ponies, too?
Isn't it already?
I see nothing in __kernel_fpu_begin that looks like it would
ever need to sleep.
- --
All rights reversed
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJUiPQyAAoJEM553pKExN6DKJoH/iWa64YibC17ADt2F7Uq4sSD
7gsi7oG7t/WJGUH5QbWy3O+36ppTw2lZwLMUUlPMqHaqzyhNa8TkGr2auyJyH45h
vk7YCBpHjzqGB8IUxgbeaie6n95Z8RG28FP8HOB1EjCwQwqJR3lQqnvRP6QD17FX
H/I9+w5+Hdkcu0sNj8jppdap+q6Bu/y1WHli3iWIlHMJIsfMMmkmiZR/Gw0ewf0w
F8bePmQYQjyB/xkEPtfXFGUuJfnbLYkYFyHUHHe/J+/MI1VkKNPDBGelvNKwniEC
41R7KinuqVh6DiAa9WprAXcrmllHI4L5aIFIRWI/W03/omFrF6WAdWs8OXioHfI=
=s4Eb
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-12-11 1:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 0:25 [PATCH, 3.18] sleeping function called from invalid context Daniel J Blueman
2014-12-11 0:37 ` Andy Lutomirski
2014-12-11 0:46 ` Daniel J Blueman
2014-12-11 0:49 ` Rik van Riel
2014-12-11 0:51 ` Andy Lutomirski
2014-12-11 1:32 ` Rik van Riel [this message]
2014-12-11 1:53 ` Andy Lutomirski
2014-12-11 2:10 ` Rik van Riel
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=5488F432.5010405@redhat.com \
--to=riel@redhat.com \
--cc=daniel@quora.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.