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=-11.7 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SPF_HELO_NONE,SPF_PASS autolearn=ham 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 13F44C4338F for ; Wed, 25 Aug 2021 10:32:43 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id ECA6861184 for ; Wed, 25 Aug 2021 10:32:42 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239784AbhHYKd0 (ORCPT ); Wed, 25 Aug 2021 06:33:26 -0400 Received: from mail.kernel.org ([198.145.29.99]:42372 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237180AbhHYKdZ (ORCPT ); Wed, 25 Aug 2021 06:33:25 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id C8BC561139; Wed, 25 Aug 2021 10:32:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1629887560; bh=riIUKt2+jXTF9OV5PivRYHe4RIB9mskvpwhkELCFFzs=; h=Subject:From:To:Cc:Date:In-Reply-To:References:From; b=NgEHl53QL1cXNSyGNVT7rkSdYOtwQyFr3rZmUDMWELpYVDmjrd0eoiB43FFuHCo/F 44VZ+YaJofRXqzZQygrdtc6G8O7gxHWFcHTJ2ABrGkMZGn79nseCxioPqSLvZvF9JQ CmJzB/XqTDYMuDjTAjEWUM/odBNaLb7LQcOsYLE/cBqqtFCVQgdGTbHcWCviOLKgQn +sE1HvhOkV2CEjkejdQX2f3k9AIn2xpN8FaNsUm4O7BEALAp8cOknCbh6kTML9npKr l1d3BbHq2Kh/YXipK7a2oMYi8myPb/HH0CMSVO/s3LufiPXIMAGAVp068Zjf/Cs3mL pT1Fv6ROk2PCw== Message-ID: Subject: Re: [fs] f7e33bdbd6: ltp.ftruncate04_64.fail From: Jeff Layton To: kernel test robot Cc: LKML , lkp@lists.01.org, lkp@intel.com, ltp@lists.linux.it Date: Wed, 25 Aug 2021 06:32:38 -0400 In-Reply-To: <20210825051710.GA5358@xsang-OptiPlex-9020> References: <20210825051710.GA5358@xsang-OptiPlex-9020> Content-Type: text/plain; charset="ISO-8859-15" User-Agent: Evolution 3.40.4 (3.40.4-1.fc34) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2021-08-25 at 13:17 +0800, kernel test robot wrote: > > Greeting, > > FYI, we noticed the following commit (built with gcc-9): > > commit: f7e33bdbd6d1bdf9c3df8bba5abcf3399f957ac3 ("fs: remove mandatory file locking support") > https://git.kernel.org/cgit/linux/kernel/git/jlayton/linux.git locks-next > > > in testcase: ltp > version: ltp-x86_64-14c1f76-1_20210821 > with following parameters: > > disk: 1HDD > fs: ext4 > test: syscalls-07 > ucode: 0xe2 > > test-description: The LTP testsuite contains a collection of tools for testing the Linux kernel and related features. > test-url: http://linux-test-project.github.io/ > > > on test machine: 4 threads Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz with 32G memory > > caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace): > > > [...] > <<>> > tag=ftruncate04_64 stime=1629792639 > cmdline="ftruncate04_64" > contacts="" > analysis=exit > <<>> > tst_device.c:89: TINFO: Found free device 0 '/dev/loop0' > tst_test.c:916: TINFO: Formatting /dev/loop0 with ext2 opts='' extra opts='' > mke2fs 1.44.5 (15-Dec-2018) > tst_test.c:1348: TINFO: Timeout per run is 0h 25m 00s > ftruncate04.c:116: TINFO: Child locks file > ftruncate04.c:49: TFAIL: ftruncate() offset before lock succeeded unexpectedly > ftruncate04.c:49: TFAIL: ftruncate() offset in lock succeeded unexpectedly > ftruncate04.c:84: TPASS: ftruncate() offset after lock succeded > ftruncate04.c:127: TINFO: Child unlocks file > ftruncate04.c:84: TPASS: ftruncate() offset in lock succeded > ftruncate04.c:84: TPASS: ftruncate() offset before lock succeded > ftruncate04.c:84: TPASS: ftruncate() offset after lock succeded > > Summary: > passed 4 > failed 2 > broken 0 > skipped 0 > warnings 0 I think this failed because of the above, which is expected now that we ignore the "mand" mount option (and mandatory locking support is gone). Oliver, you may need to update the expected test output for this test. Thanks, -- Jeff Layton