From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f71.google.com (mail-wm0-f71.google.com [74.125.82.71]) by kanga.kvack.org (Postfix) with ESMTP id A8D746B026D for ; Tue, 19 Dec 2017 03:37:53 -0500 (EST) Received: by mail-wm0-f71.google.com with SMTP id b82so761595wmd.5 for ; Tue, 19 Dec 2017 00:37:53 -0800 (PST) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com. [66.111.4.27]) by mx.google.com with ESMTPS id g32si4744713edb.218.2017.12.19.00.37.52 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 19 Dec 2017 00:37:52 -0800 (PST) Date: Tue, 19 Dec 2017 19:37:46 +1100 From: "Tobin C. Harding" Subject: Re: BUG: bad usercopy in memdup_user Message-ID: <20171219083746.GR19604@eros> References: <001a113e9ca8a3affd05609d7ccf@google.com> <6a50d160-56d0-29f9-cfed-6c9202140b43@I-love.SAKURA.ne.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: owner-linux-mm@kvack.org List-ID: To: Dmitry Vyukov Cc: Kees Cook , Tetsuo Handa , Linux-MM , syzbot , David Windsor , keun-o.park@darkmatter.ae, Laura Abbott , LKML , Mark Rutland , Ingo Molnar , syzkaller-bugs@googlegroups.com, Will Deacon On Tue, Dec 19, 2017 at 09:12:58AM +0100, Dmitry Vyukov wrote: > On Tue, Dec 19, 2017 at 1:57 AM, Kees Cook wrote: > > On Mon, Dec 18, 2017 at 6:22 AM, Tetsuo Handa > > wrote: > >> On 2017/12/18 22:40, syzbot wrote: > >>> Hello, > >>> > >>> syzkaller hit the following crash on 6084b576dca2e898f5c101baef151f7bfdbb606d > >>> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master > >>> compiler: gcc (GCC) 7.1.1 20170620 > >>> .config is attached > >>> Raw console output is attached. > >>> > >>> Unfortunately, I don't have any reproducer for this bug yet. > >>> > >>> > >> > >> This BUG is reporting > >> > >> [ 26.089789] usercopy: kernel memory overwrite attempt detected to 0000000022a5b430 (kmalloc-1024) (1024 bytes) > >> > >> line. But isn't 0000000022a5b430 strange for kmalloc(1024, GFP_KERNEL)ed kernel address? > > > > The address is hashed (see the %p threads for 4.15). > > > +Tobin, is there a way to disable hashing entirely? The only > designation of syzbot is providing crash reports to kernel developers > with as much info as possible. It's fine for it to leak whatever. We have new specifier %px to print addresses in hex if leaking info is not a worry. Hope this helps, Tobin. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org