From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1754897AbcBGVxi (ORCPT <rfc822;w@1wt.eu>);
	Sun, 7 Feb 2016 16:53:38 -0500
Received: from mail-wm0-f46.google.com ([74.125.82.46]:38267 "EHLO
	mail-wm0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1750749AbcBGVxg (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Sun, 7 Feb 2016 16:53:36 -0500
From: Rasmus Villemoes <linux@rasmusvillemoes.dk>
To: Kees Cook <keescook@chromium.org>
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>,
        Andrew Morton <akpm@linux-foundation.org>,
        LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] vsprintf: kptr_restrict is okay in IRQ when 2
Organization: D03
References: <CAGXu5jK02bj4XxRE60zXQFToDcHGRKY57E0k6-W23+Br9vyKjA@mail.gmail.com>
	<1454709783-17385-1-git-send-email-Jason@zx2c4.com>
	<CAGXu5jKGG7c0YoO_uQvDEFqgG1gWtfcfpm3yaeVeuzdO4-LPVQ@mail.gmail.com>
X-Hashcash: 1:20:160207:jason@zx2c4.com::aCTiSoZfu5XlBcf5:000FZ+
X-Hashcash: 1:20:160207:linux-kernel@vger.kernel.org::l6ZTybevd/lLvKsX:0000000000000000000000000000000000VM1
X-Hashcash: 1:20:160207:akpm@linux-foundation.org::sHJVPC2eP7yFY6q+:0000000000000000000000000000000000000aos
X-Hashcash: 1:20:160207:keescook@chromium.org::OyfohZAqQv1E8pA7:0000000000000000000000000000000000000000A4hI
Date: Sun, 07 Feb 2016 22:53:34 +0100
In-Reply-To: <CAGXu5jKGG7c0YoO_uQvDEFqgG1gWtfcfpm3yaeVeuzdO4-LPVQ@mail.gmail.com>
	(Kees Cook's message of "Fri, 5 Feb 2016 14:14:18 -0800")
Message-ID: <87zivcdw69.fsf@rasmusvillemoes.dk>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Fri, Feb 05 2016, Kees Cook <keescook@chromium.org> wrote:

>>                 switch (kptr_restrict) {
>>                 case 0:
>>                         /* Always print %pK values */
>>                         break;
>>                 case 1: {
>> +                       const struct cred *cred;
>> +
>> +                       /*
>> +                        * kptr_restrict==2 cannot be used in IRQ context because
                                             ^

should be 1, right?

Rasmus