All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Sasha Levin <sasha.levin@oracle.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Dave Jones <davej@redhat.com>, Michal Hocko <mhocko@suse.cz>,
	Borislav Petkov <bp@alien8.de>,
	"the arch\/x86 maintainers" <x86@kernel.org>
Subject: Re: Hang on large copy_from_user with PREEMPT_NONE
Date: Tue, 07 Apr 2015 11:19:05 +0930	[thread overview]
Message-ID: <87bnj03dym.fsf@rustcorp.com.au> (raw)
In-Reply-To: <CA+55aFz8gByWhuAgW4fER8uw=q9E=tcN6LeS3YqCOqYsOfwPxA@mail.gmail.com>

Linus Torvalds <torvalds@linux-foundation.org> writes:
> Alternatively, we could just limit module loading size to some (fairly
> arbitrary) big number.

Yeah, we used to do that because vmalloc would BUG rather than
returning NULL.

But you're already CAP_SYS_MODULE in this path, which kind of makes it
hard to care very much about it being slow under virtualization.

Cheers,
Rusty.

  reply	other threads:[~2015-04-08  1:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-06  3:59 Hang on large copy_from_user with PREEMPT_NONE Sasha Levin
2015-04-06 11:24 ` Borislav Petkov
2015-04-06 14:51   ` Sasha Levin
2015-04-06 16:52     ` Borislav Petkov
2015-04-06 17:26 ` Linus Torvalds
2015-04-06 19:08   ` Sasha Levin
2015-04-06 19:36     ` Borislav Petkov
2015-04-06 23:45       ` Sasha Levin
2015-04-06 20:42     ` Linus Torvalds
2015-04-07  1:49       ` Rusty Russell [this message]
2015-04-07  9:31       ` Ingo Molnar
2015-04-07 10:39         ` Borislav Petkov
2015-04-07 11:05           ` Ingo Molnar
2015-04-07 14:30             ` Michal Hocko
2015-04-07 14:37               ` Ingo Molnar
2015-04-07 17:00                 ` Sasha Levin
2015-04-07 17:33                   ` Linus Torvalds
2015-04-07 17:58                     ` Dave Jones
     [not found]                       ` <CA+55aFyxCb9aDfh0L4gyvHMSefOFoD7zftRpWbnvf5j9iZVaMw@mail.gmail.com>
2015-04-07 21:09                         ` Dave Jones

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=87bnj03dym.fsf@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=bp@alien8.de \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhocko@suse.cz \
    --cc=sasha.levin@oracle.com \
    --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 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.