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=-2.4 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_2 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 C9EEFC3A5A5 for ; Tue, 3 Sep 2019 18:15:54 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id A524122D6D for ; Tue, 3 Sep 2019 18:15:54 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lca.pw header.i=@lca.pw header.b="n0858ChS" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730076AbfICSPx (ORCPT ); Tue, 3 Sep 2019 14:15:53 -0400 Received: from mail-qt1-f175.google.com ([209.85.160.175]:34018 "EHLO mail-qt1-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727667AbfICSPx (ORCPT ); Tue, 3 Sep 2019 14:15:53 -0400 Received: by mail-qt1-f175.google.com with SMTP id a13so21122039qtj.1 for ; Tue, 03 Sep 2019 11:15:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lca.pw; s=google; h=message-id:subject:from:to:cc:date:in-reply-to:references :mime-version:content-transfer-encoding; bh=ZDlL/rClenmR6VE0siOjkh2adGJaq3G/Ew8VVSvBXFQ=; b=n0858ChSPnxrWGFDol00Hg+lvhh8YIO8MRJ/Doeyn7XYhB2te+tGPYU0t/DifI5YC8 bdhHUVkfoaYtcIL4eluO4sMEL+cSQsvT9qZXaURgkrEfbuCSCm0hcfmR+os3wOax7yZT QKYB2d5Zl3Gng+m1l6H/UI2pLc0Z0zQC9SFD1UGBDgQ/MyoG7i/CCChWhBao5TRTVkHi yvvTzimrjKOuepwnAo7DUVbpCZYvuOHIYsH/R7lvdqfSOAU6EVysLASUq7+9RLwrBvBl vbyQ+EFCCft4ZJ8LcKnxhWbFEtwVY7QQbpGIWQ+ny5TioowSH2W0AqA6VjqscIIAM94g pEGw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:mime-version:content-transfer-encoding; bh=ZDlL/rClenmR6VE0siOjkh2adGJaq3G/Ew8VVSvBXFQ=; b=VM10vOb2uW4Xlhbek9PvM/UYpBrTECm46t+XV/cmTriOLZk8LyEnopkNEivu81bZae stE8xcZJCSjYrAgpoD+vDsnqBNYlEzrNvNIztNcRnx167U9d60KptxDphOQ1RMDu7PS6 f+rbOAqPcSzp2vuAo7IsunTZUTq5ljNyZAVHa06tvwvS0cNpvr0n1D2utM3OdTqNlmGU hSLvLVouYAx2sraS6wkHLKCYxHEAUXBezwpoIE3UzqFV62259EEL/zuWTMY+oX3X2N8G kB7Q639ZSZ0kenoR7ftUR4Gq19Sp08K5Oh2ltUFjhPeyalv6rc+DOpszf2aGjJLYdSEW uwFQ== X-Gm-Message-State: APjAAAW9/13y1x5zct6T8GtDD0bxsnFJAVrOx4NMJsmtFMmR0McfVCn8 iKqYXtKd8d84TErUaNwU4dqmBg== X-Google-Smtp-Source: APXvYqzCEa99BG6PuKfmnoHXjuYaVJwIQTmH16PtTHa3ItgXKrqdjCBIygS49mE4aOzrypG8zKA/+A== X-Received: by 2002:ac8:5204:: with SMTP id r4mr16151539qtn.332.1567534552343; Tue, 03 Sep 2019 11:15:52 -0700 (PDT) Received: from dhcp-41-57.bos.redhat.com (nat-pool-bos-t.redhat.com. [66.187.233.206]) by smtp.gmail.com with ESMTPSA id u22sm8086968qtq.13.2019.09.03.11.15.50 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 03 Sep 2019 11:15:51 -0700 (PDT) Message-ID: <1567534549.5576.62.camel@lca.pw> Subject: Re: "beyond 2038" warnings from loopback mount is noisy From: Qian Cai To: Deepa Dinamani Cc: Jeff Layton , Alexander Viro , Linux FS-devel Mailing List , Linux Kernel Mailing List , Theodore Ts'o , Ext4 Developers List , Andreas Dilger , Arnd Bergmann Date: Tue, 03 Sep 2019 14:15:49 -0400 In-Reply-To: References: <1567523922.5576.57.camel@lca.pw> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.22.6 (3.22.6-10.el7) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 2019-09-03 at 09:36 -0700, Deepa Dinamani wrote: > We might also want to consider updating the file system the LTP is > being run on here. It simply format (mkfs.ext4) a loop back device on ext4 with the kernel. CONFIG_EXT4_FS=m # CONFIG_EXT4_USE_FOR_EXT2 is not set # CONFIG_EXT4_FS_POSIX_ACL is not set # CONFIG_EXT4_FS_SECURITY is not set # CONFIG_EXT4_DEBUG is not set using e2fsprogs-1.44.6. Do you mean people now need to update the kernel to enable additional config to avoid the spam of warnings now?