Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753517AbdFVUv0 (ORCPT ); Thu, 22 Jun 2017 16:51:26 -0400 Received: from mx1.redhat.com ([209.132.183.28]:35254 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752392AbdFVUvY (ORCPT ); Thu, 22 Jun 2017 16:51:24 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com F3A5541A54 Authentication-Results: ext-mx06.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx06.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=oleg@redhat.com DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com F3A5541A54 Date: Thu, 22 Jun 2017 22:51:15 +0200 From: Oleg Nesterov To: Hugh Dickins Cc: Linus Torvalds , Cyrill Gorcunov , Andrey Vagin , Pavel Emelyanov , Dmitry Safonov , Andrew Morton , Adrian Reber , Michael Kerrisk , Willy Tarreau , kernel test robot , Michal Hocko , LKML , LKP , Larry Woodman , Rik van Riel Subject: Re: [lkp-robot] [mm] 1be7107fbe: kernel_BUG_at_mm/mmap.c Message-ID: <20170622205115.GA4938@redhat.com> References: <20170621193338.GA29222@redhat.com> <20170621202751.GA29638@redhat.com> <20170621205617.GA29841@redhat.com> <20170622151623.GB762@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.30]); Thu, 22 Jun 2017 20:51:24 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 889 Lines: 23 On 06/22, Hugh Dickins wrote: > > On Thu, 22 Jun 2017, Oleg Nesterov wrote: > > > > Something like the patch below? Yes, I thought about this too. > > Yes, that patch (times 11 for all the architectures) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Yes, yes, this is clear to me. But only after you have already explained this in your previous email ;) > But my own preference this morning is to do nothing, until we hear > more complaints and can classify them as genuine userspace breakage, > as opposed to testcases surprised by a new kernel implementation. OK. Agreed. Lets wait for the "real" bug report. FYI. I am still investigating that redhat internal bug report. And yes, it was the real application. But. I still think that it fails by another reason, just the test-case they provided doesn't match the reality and it hits another (this) problem by accident. Oleg.