All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Andy Lutomirski <luto@amacapital.net>,
	Ingo Molnar <mingo@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH] x86: Verify access_ok() context
Date: Tue, 22 Nov 2016 11:42:19 -0800	[thread overview]
Message-ID: <CA+55aFzUq8uqsJyZRdNy4Rt11L561YcahwtTkHNU3Y2LeXGJEw@mail.gmail.com> (raw)
In-Reply-To: <20161122193720.GA3045@worktop.programming.kicks-ass.net>

On Tue, Nov 22, 2016 at 11:37 AM, Peter Zijlstra <peterz@infradead.org> wrote:
>
> CONFIG_DEBUG_VM seems somehow inappropriate.

The usual might_fault() logic? That uses

    defined(CONFIG_PROVE_LOCKING) || defined(CONFIG_DEBUG_ATOMIC_SLEEP)

(and "might_sleep()" uses just CONFIG_DEBUG_ATOMIC_SLEEP, maybe that's fine).

               Linus

  reply	other threads:[~2016-11-22 19:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-22  9:57 [RFC][PATCH] x86: Verify access_ok() context Peter Zijlstra
2016-11-22 17:28 ` Andy Lutomirski
2016-11-22 19:37   ` Peter Zijlstra
2016-11-22 19:42     ` Linus Torvalds [this message]
2016-12-05 10:27       ` Peter Zijlstra
2017-01-16 20:27         ` David Smith
2017-01-16 21:14           ` Thomas Gleixner
2017-01-18 22:16             ` David Smith
2017-01-19  0:19               ` Andy Lutomirski
2017-01-19 15:37                 ` David Smith
2017-01-20  8:24                 ` Peter Zijlstra
2017-01-20  8:50                   ` Thomas Gleixner
2017-01-19 18:12               ` Thomas Gleixner
2017-01-19 20:22                 ` Frank Ch. Eigler
2017-01-19 20:50                   ` Thomas Gleixner
2017-01-19 21:27                     ` Frank Ch. Eigler
2017-01-19 22:20                       ` Peter Zijlstra
2017-01-19 23:04                       ` Thomas Gleixner

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=CA+55aFzUq8uqsJyZRdNy4Rt11L561YcahwtTkHNU3Y2LeXGJEw@mail.gmail.com \
    --to=torvalds@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /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.