[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGXu5jLZGW8sodoNw6h+BWxnAGjpW0HTMEjx=Ee9AZ6PgVwX4A@mail.gmail.com>
Date: Tue, 19 Dec 2017 13:54:56 -0800
From: Kees Cook <keescook@...omium.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Matthew Wilcox <willy@...radead.org>,
"Tobin C. Harding" <me@...in.cc>,
Dmitry Vyukov <dvyukov@...gle.com>,
Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>,
Linux-MM <linux-mm@...ck.org>,
syzbot
<bot+719398b443fd30155f92f2a888e749026c62b427@...kaller.appspotmail.com>,
David Windsor <dave@...lcore.net>, keun-o.park@...kmatter.ae,
Laura Abbott <labbott@...hat.com>,
LKML <linux-kernel@...r.kernel.org>,
Mark Rutland <mark.rutland@....com>,
Ingo Molnar <mingo@...nel.org>,
syzkaller-bugs@...glegroups.com, Will Deacon <will.deacon@....com>
Subject: Re: BUG: bad usercopy in memdup_user
On Tue, Dec 19, 2017 at 1:36 PM, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
> In this case, there's obviously no permission issue: it's an error
> report. So it's either "remove it, or switch to %px".
Yup, my intention was to kill this %p and enhance the report to
actually include the useful information like, "what is the offset from
the start of the object", etc. That's what really matters.
-Kees
--
Kees Cook
Pixel Security
Powered by blists - more mailing lists