[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wj2MDhU05UiR26Rn6+uywgwZPE134hPBOuLwKwFs=_GKw@mail.gmail.com>
Date: Tue, 18 Feb 2020 12:21:20 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Ilya Dryomov <idryomov@...il.com>
Cc: Adam Borowski <kilobyte@...band.pl>,
Kees Cook <keescook@...omium.org>,
LKML <linux-kernel@...r.kernel.org>,
Petr Mladek <pmladek@...e.com>,
Steven Rostedt <rostedt@...dmis.org>,
Randy Dunlap <rdunlap@...radead.org>,
Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
"Tobin C . Harding" <me@...in.cc>
Subject: Re: [PATCH] vsprintf: don't obfuscate NULL and error pointers
On Tue, Feb 18, 2020 at 12:18 PM Ilya Dryomov <idryomov@...il.com> wrote:
>
> > %p: 0000000001f8cc5b -EFAULT NULL
>
> ^^^
> I assume you meant %pe here.
Heh, yes.
> Looks sensible to me. Without this patch NULL is obfuscated for
> both %p and %pe though. Do you want this patch amended or prefer
> a follow-up for %pe "0000000000000000" -> "NULL" so that it can be
> discussed separately?
Yeah, as an independent follow-up. I think your first patch is fine,
and I think this %pe NULL behavior thing is a completely separate
issue that just came up when %pe was mentioned.
Linus
Powered by blists - more mailing lists