From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Stancek Date: Fri, 17 Jan 2020 03:35:11 -0500 (EST) Subject: [LTP] ??? FAIL: Test report for kernel 5.4.13-rc1-7f1b863.cki (stable) In-Reply-To: <20200116153741.GA558@rei> References: <84944fa0-3c18-f8a4-47ca-7627eb4e0594@redhat.com> <20200116153741.GA558@rei> Message-ID: <1477632721.2420697.1579250111441.JavaMail.zimbra@redhat.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ltp@lists.linux.it ----- Original Message ----- > Hi! > > > One or more kernel tests failed: > > > > > > ppc64le: > > > ??? LTP > > > > Hi, I see max_map_count failed on ppc64le: > > https://artifacts.cki-project.org/pipelines/385189/logs/ppc64le_host_2_LTP_mm.run.log > > That's strange, we do attempt to map 65536 mappings but we do not touch > them, so these shouldn't be faulted in, so there is no real reason why > mmap() in the child process should stop prematurely at 65532. > > I guess that we cannot do much here, unless it's reproducible, because > there is not much information there. max_map_count.c:205: FAIL: 64882 map entries in total, but expected 65536 entries I can reproduce it by running it in loop for couple hours. Though no idea why we started seeing it only in 5.4.13 rc kernels, as there doesn't seem to be any significant mm changes. I'll try some older kernels. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.9 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 7A739C33CB1 for ; Fri, 17 Jan 2020 08:35:23 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 501A820728 for ; Fri, 17 Jan 2020 08:35:23 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="Xo/AyUGO" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729690AbgAQIfW (ORCPT ); Fri, 17 Jan 2020 03:35:22 -0500 Received: from us-smtp-delivery-1.mimecast.com ([207.211.31.120]:52415 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727002AbgAQIfV (ORCPT ); Fri, 17 Jan 2020 03:35:21 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1579250119; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=8Yhtv60kTBgLbtrf5+KxVHz2BHqtcVn/8f147NS0+So=; b=Xo/AyUGOolNmks53vZoo/3ptjKKC+xDJa4HBzCh2JqM9tpkVQkTgrqQ4nUh0FaQlZYCPOx HrcYF+K/6UDfexubAoYeIC9hPzKTvYywVDxQTTySpuCgsjJgM03+aYVLJDf8tUXElzilA9 zk1oSx+zCYciNdPt8m+UXbt7Mv/9ryE= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-385-px9lVYfWP7CngCFPjmpKhg-1; Fri, 17 Jan 2020 03:35:13 -0500 X-MC-Unique: px9lVYfWP7CngCFPjmpKhg-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 99F548017CC; Fri, 17 Jan 2020 08:35:12 +0000 (UTC) Received: from colo-mx.corp.redhat.com (colo-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.20]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 90E4B10016EB; Fri, 17 Jan 2020 08:35:12 +0000 (UTC) Received: from zmail17.collab.prod.int.phx2.redhat.com (zmail17.collab.prod.int.phx2.redhat.com [10.5.83.19]) by colo-mx.corp.redhat.com (Postfix) with ESMTP id DB8431809563; Fri, 17 Jan 2020 08:35:11 +0000 (UTC) Date: Fri, 17 Jan 2020 03:35:11 -0500 (EST) From: Jan Stancek To: Cyril Hrubis Cc: Rachel Sibley , Jianwen Ji , Hangbin Liu , Memory Management , Linux Stable maillist , Jianlin Shi , CKI Project , LTP Mailing List Message-ID: <1477632721.2420697.1579250111441.JavaMail.zimbra@redhat.com> In-Reply-To: <20200116153741.GA558@rei> References: <84944fa0-3c18-f8a4-47ca-7627eb4e0594@redhat.com> <20200116153741.GA558@rei> Subject: Re: [LTP] ??? FAIL: Test report for kernel 5.4.13-rc1-7f1b863.cki (stable) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [10.43.17.25, 10.4.195.6] Thread-Topic: ??? FAIL: Test report for kernel 5.4.13-rc1-7f1b863.cki (stable) Thread-Index: p1YXf2kW0X2fHt0OMwa/2fDBBYA+iw== X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 Sender: stable-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org ----- Original Message ----- > Hi! > > > One or more kernel tests failed: > > > > > > ppc64le: > > > ??? LTP > > > > Hi, I see max_map_count failed on ppc64le: > > https://artifacts.cki-project.org/pipelines/385189/logs/ppc64le_host_2_LTP_mm.run.log > > That's strange, we do attempt to map 65536 mappings but we do not touch > them, so these shouldn't be faulted in, so there is no real reason why > mmap() in the child process should stop prematurely at 65532. > > I guess that we cannot do much here, unless it's reproducible, because > there is not much information there. max_map_count.c:205: FAIL: 64882 map entries in total, but expected 65536 entries I can reproduce it by running it in loop for couple hours. Though no idea why we started seeing it only in 5.4.13 rc kernels, as there doesn't seem to be any significant mm changes. I'll try some older kernels.