All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Linus Torvalds <torvalds@osdl.org>
Cc: linux-kernel@vger.kernel.org, gk@garethknight.com
Subject: Re: [PATCH] generic signal code (small new feature - userspace signal mask), kernel 2.6.16
Date: 16 Oct 2006 15:28:39 +0200	[thread overview]
Message-ID: <p731wp8e6ew.fsf@verdi.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0610152025300.3962@g5.osdl.org>

Linus Torvalds <torvalds@osdl.org> writes:
> 
> Why? You're doing user-space accesses from within critical sections with a 
> spinlock, and that's just a big no-no. Think page faults, swapping etc.

He could pin the page in memory like futexes do. One page pinned
per thread shouldn't be a big DOS issue either.

-Andi

  parent reply	other threads:[~2006-10-16 13:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-16  3:04 [PATCH] generic signal code (small new feature - userspace signal mask), kernel 2.6.16 Gareth Knight
2006-10-16  3:37 ` Linus Torvalds
2006-10-16  3:50   ` Gareth Knight
2006-10-16 13:28   ` Andi Kleen [this message]
2006-10-16 23:15     ` Nicholas Miell
  -- strict thread matches above, loose matches on Subject: below --
2006-10-17  9:24 linux
2006-10-17 12:32 ` Gareth Knight

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=p731wp8e6ew.fsf@verdi.suse.de \
    --to=ak@suse.de \
    --cc=gk@garethknight.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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.