Received: by 2002:a17:90b:8d0:0:0:0:0 with SMTP id ds16csp4744193pjb; Mon, 27 Jul 2020 04:09:25 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxJE4zRR2f7ZKr6vuy8gcG/Ig95Ma0vL7TImR+l5YwoHShwk590rfTNQVSK1TR343mX6GAW X-Received: by 2002:aa7:d7d7:: with SMTP id e23mr4612507eds.347.1595848164996; Mon, 27 Jul 2020 04:09:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1595848164; cv=none; d=google.com; s=arc-20160816; b=XLuh3SYvnXpdEHnH8omLZYa85ooAHje4eJqwYCmJYspfbBpKCaibDeKswz2I6YbBvc LjMsAdKRBL5H2acRNUOadkeo4kr6u46BVTh8rn7laW3rNOfIgIQbnAE149LmbFFLi57m FUl7FsnWBlVVBJbf6CHPVcYd9tPn+vOscrOVBQjJlQvwRIWPQhVa1fcQvRFmCTwoJYTT cN6mhNwBwWxOnlqqwWgJ1nEL1fAOimYeIM5xX7bepe2IV/7LE1dxYYCjWiut5/Tk7Ig6 xn5Ud40A+KHH1MakgNRtw5eIh7aNXgw5kZlh8Zi9IO3cXeueTEIEqhS5CHnUt0zgj22K I1LQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=CH3w9r5mSG8UwTMprvobZ7CguxfX3cg4vtOp/DjFAAU=; b=a81YhPzhGFRTXjnUnKIKXqL4nU2paLsRu6d2CymZon629EXVmiU2VlfFRQk3sy89zw MxmffCkY7RlU+vhbYEyZy2kvPtcoizRpIgmy28uh8JE6IVWCqVqSe/PYHGPkf1AjeV/N t4WAPrhjgOJELm0H0tIeSdbPPgn0pRrdp3De6qpUJWu8Ng0E6mNZDKcm5C+4NL3gFMx+ QcHe0san5Y1Fw9jfeb7578n6ZRvi/srmRy3nafF8S9axW/BZkg/95YBVFhs0ny+zKaho sNwTHU5wfAXD4xkS31ELZ/FmzNYJGIOsmAyWJfneoUhdjrWFK3icSDcq4drm1t1UY8hi Dg1w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id o17si5440486ejg.160.2020.07.27.04.09.03; Mon, 27 Jul 2020 04:09:24 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728325AbgG0Kvu (ORCPT + 99 others); Mon, 27 Jul 2020 06:51:50 -0400 Received: from mx2.suse.de ([195.135.220.15]:45294 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726298AbgG0Kvu (ORCPT ); Mon, 27 Jul 2020 06:51:50 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id 76F5FB615; Mon, 27 Jul 2020 10:51:59 +0000 (UTC) Date: Mon, 27 Jul 2020 12:52:10 +0200 From: Cyril Hrubis To: Petr Vorel Cc: kernel test robot , Jens Axboe , Sagi Grimberg , LKML , Ming Lei , Christoph Hellwig , lkp@lists.01.org, Baolin Wang , Christoph Hellwig , ltp@lists.linux.it Subject: Re: [LTP] [blk] 6e6fcbc27e: ltp.fs_fill.fail Message-ID: <20200727105210.GA12348@yuki.lan> References: <20200726075511.GI1850@shao2-debian> <20200727093156.GA29739@dell5510> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200727093156.GA29739@dell5510> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi! > > tst_test.c:1308: INFO: Testing on vfat > > tst_mkfs.c:90: INFO: Formatting /dev/loop0 with vfat opts='' extra opts='' > > tst_test.c:1247: INFO: Timeout per run is 0h 05m 00s > > fs_fill.c:103: INFO: Running 10 writer threads > > Test timeouted, sending SIGKILL! > > Test timeouted, sending SIGKILL! > > Test timeouted, sending SIGKILL! > > Test timeouted, sending SIGKILL! > > Test timeouted, sending SIGKILL! > > Test timeouted, sending SIGKILL! > The only "error" I found is that fs_fill test timeouted on vfat. That might > indicate some problems. Note, for slow machines, there is LTP_TIMEOUT_MUL > https://github.com/linux-test-project/ltp/wiki/User-Guidelines#1-library-environment-variables Actually you had removed the most important part, it not only timeouted but the process ended up stuck in kernel and could not be killed. So this looks like deadlock somewhere in filesystem code. -- Cyril Hrubis chrubis@suse.cz