linux-kernel - Re: [PATCH v2] vsprintf: kptr_restrict is okay in IRQ when 2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87zivcdw69.fsf@rasmusvillemoes.dk>
Date:	Sun, 07 Feb 2016 22:53:34 +0100
From:	Rasmus Villemoes <linux@...musvillemoes.dk>
To:	Kees Cook <keescook@...omium.org>
Cc:	"Jason A. Donenfeld" <Jason@...c4.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] vsprintf: kptr_restrict is okay in IRQ when 2

On Fri, Feb 05 2016, Kees Cook <keescook@...omium.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