From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752432AbcHIBUw (ORCPT ); Mon, 8 Aug 2016 21:20:52 -0400 Received: from mga01.intel.com ([192.55.52.88]:15674 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752065AbcHIBUv (ORCPT ); Mon, 8 Aug 2016 21:20:51 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.28,493,1464678000"; d="scan'208";a="152711063" Date: Tue, 9 Aug 2016 09:17:58 +0800 From: Ye Xiaolong To: Valdis.Kletnieks@vt.edu Cc: Nicholas Krause , 0day robot , LKML , lkp@01.org Subject: Re: [lkp] [fs] 45ec18d5c7: BUG: KASAN: user-memory-access on address 00007f90291c7ec0 Message-ID: <20160809011758.GE8581@yexl-desktop> References: <20160807140242.GA21617@yexl-desktop> <17429.1470673783@turing-police.cc.vt.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <17429.1470673783@turing-police.cc.vt.edu> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 08/08, Valdis.Kletnieks@vt.edu wrote: >On Sun, 07 Aug 2016 22:02:42 +0800, kernel test robot said: > >> FYI, we noticed the following commit: >> >> https://github.com/0day-ci/linux >> Nicholas-Krause/fs-Fix-kmemleak-leak-warning-in-getname_flags-about-working-on-unitialized-memory/20160804-055054 >> commit 45ec18d5c713bccb9807782f0dca29b92ba99784 ("fs:Fix kmemleak leak warning in getname_flags about working on unitialized memory") > >The real question here is why the 0day system was even bothering to try >compiling and booting a patch from somebody who has a long record of failing >to do so with patches before submission. Actually looking at the patch >in question shows that little or no thought or testing was done (hint: >look at it, and wonder in amazement why there's a dump_stack() call where >it is....) > >In other words - how did this patch get into a tree that 0day listens to? 0Day has a service to automatically capture every patchset sent to LKML, and convert email patchset to git branches by applying them on top of different trees heuristically.