From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932125AbcHHQ3z (ORCPT ); Mon, 8 Aug 2016 12:29:55 -0400 Received: from outbound.smtp.vt.edu ([198.82.183.121]:40194 "EHLO omr1.cc.vt.edu" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752125AbcHHQ3x (ORCPT ); Mon, 8 Aug 2016 12:29:53 -0400 X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.6+dev To: kernel test robot Cc: Nicholas Krause , 0day robot , LKML , lkp@01.org Subject: Re: [lkp] [fs] 45ec18d5c7: BUG: KASAN: user-memory-access on address 00007f90291c7ec0 From: Valdis.Kletnieks@vt.edu In-Reply-To: <20160807140242.GA21617@yexl-desktop> References: <20160807140242.GA21617@yexl-desktop> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1470673783_2013P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Mon, 08 Aug 2016 12:29:43 -0400 Message-ID: <17429.1470673783@turing-police.cc.vt.edu> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --==_Exmh_1470673783_2013P Content-Type: text/plain; charset=us-ascii 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? --==_Exmh_1470673783_2013P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Exmh version 2.5 07/13/2001 iQIVAwUBV6izdwdmEQWDXROgAQIpvBAAgIuipi4yHJzs3XmuSFL3WSl4cReD6Qir OYmME+yUa+m4SjCas9BpD83a9PpmI13PtxxJGAgLZOv6YeRr9ADER83sgds9LvsA KLCraVtGHHP0le4VHSRBmAXmPYShcmPQnLY2D0cjySuD9lQ8sJvgMsHsUhOdnlIw Oq1lv7gHuPC0sqeIpdnL/kWDy5xB2BsoDhGPZjpHKbzGvFFJK4X1EqaA4TU9aQEA /CGMZiXmyLwRyNaDWAgL1jq6fsaeLFA9PKAwkZD1BP7eV6+/3hfI34+tf2GY+mZT 1KL37PWXPoHul0T9Ksv4PnguGB3vPgwmNahpPiAptJ+Cgh9j0yiu5pgmTgZOX2bo 4hHyvPXCZRi3rfAMXkjcKYHTrLNIxUVDrvQrRiCW/8qC1wcvTyMyZPVg4YXYjlLW ziRKGa+q6ZeRVtKXDmEeq6wVAY+cm6OhQPJpYvrk5ff7K/fA5bquuk4m8QahQr8C 9g/GgMieYdwxldQ7zCNIi66ULbxAvGrpjdhiTJ30P0wvaTNhUkCqfUgAe0Z5ue3C QZ64YIKP+oKZkec4iR8kQfv4NpIV8IPDoqLrfFHdnGHLdlyR6n9TkNTE/2kIu7Zw 4dhpIJsD3SgYwkjUGc4x5KGxKL6n/36SJvAS926c6YREnsILoVvld+95jnIU7CHH Wds1yiKNkiE= =6Q/y -----END PGP SIGNATURE----- --==_Exmh_1470673783_2013P--