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.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED 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 8E586C433FF for ; Sat, 10 Aug 2019 20:45:16 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 6281621743 for ; Sat, 10 Aug 2019 20:45:16 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="EnyNaVfR" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726488AbfHJUpM (ORCPT ); Sat, 10 Aug 2019 16:45:12 -0400 Received: from mail-ot1-f67.google.com ([209.85.210.67]:41856 "EHLO mail-ot1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726233AbfHJUpK (ORCPT ); Sat, 10 Aug 2019 16:45:10 -0400 Received: by mail-ot1-f67.google.com with SMTP id o101so10889669ota.8; Sat, 10 Aug 2019 13:45:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=OxgKq0uvzgCy9T3HtT1FHqYi+XIOfhSX9HlOxN06+Q4=; b=EnyNaVfR6RBYyx+WdJpxHBqOGXStQ1CR0UViT9LmJrhpXHZ5Alpzl4erD6vu8UVFzM I9CJTMHWXU4ehhHPipZ1rmTYULmZPQS9rqB4pma/8MFzAww89hM3o+6zHWAa7dmgisgt 4WgI36e6M1CT1qGPrFHWP3AKge2nY1sqhCZyFZ3BT9r5q+aVkdJDQelvthvwqDNcrf3A ukr13yXnMF6hyqJlgsj20W7fvSREYyhh/OXa6WJp4gunXU6tyXU+4l8lfSJsTMBUFAgc g+4efOCXNnsp8NIVq/EGXOAB2FssqWCGILegUSJntnVYC9oC3k1MPhSjmaI3wmHj0vNh OifQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=OxgKq0uvzgCy9T3HtT1FHqYi+XIOfhSX9HlOxN06+Q4=; b=pLacBFqNSqow4FejV7dGsE5xePHaWuMdWp3n1tUASRaDftLkHVzPeiQQhUAeeUIbVK DyG+vPRJF68PnBWaxHLCMjWTbvqplmcNwMpqikbBSA6ZUMntVrGoE/TLn+7aTxnlsJ4E kLtrkZQn5970AxH0h8g+8CiAe9MLOelco6jxJFUqZ3KhnYG2A0qRY9iB49k0l8Iph2/7 QhycdomXpMVSN/VfmOwLG8AuoI6LXAu0d9MfQnYCw3ZRG/ND+BPWQEDVrCnDBlVAN9vb wr6zxR2c9FrHWy99q8Xcp9MhbaF9yv2QjMGeNgPPwtMTcAinj7U2DNNMQd7EbwUD4pBP z+Nw== X-Gm-Message-State: APjAAAWCOmkWaWE/q28XM3AcbXyVIDCMZdJvw5CJvCA2Pr/p6bhHOf3f f8PLpIKbgSsHGO18ElJRviVMGBQVrxEBqKtZ21l5sw== X-Google-Smtp-Source: APXvYqyLFLjwXOVFOcYFXPODdfCLOQdnEaEv3OW/QjfpGeANuOjHLCLd/XzqkJzMQdfsBj81W8y7nvyUQG5WyUUUgKs= X-Received: by 2002:a02:10:: with SMTP id 16mr15375851jaa.96.1565469909350; Sat, 10 Aug 2019 13:45:09 -0700 (PDT) MIME-Version: 1.0 References: <20190730014924.2193-1-deepa.kernel@gmail.com> <20190730014924.2193-5-deepa.kernel@gmail.com> In-Reply-To: From: Deepa Dinamani Date: Sat, 10 Aug 2019 13:44:57 -0700 Message-ID: Subject: Re: [Y2038] [PATCH 04/20] mount: Add mount warning for impending timestamp expiry To: Ben Hutchings Cc: Alexander Viro , Linux Kernel Mailing List , Linux FS-devel Mailing List , y2038 Mailman List , Arnd Bergmann Content-Type: text/plain; charset="UTF-8" Sender: linux-fsdevel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org On Mon, Aug 5, 2019 at 7:14 AM Ben Hutchings wrote: > > On Mon, 2019-07-29 at 18:49 -0700, Deepa Dinamani wrote: > > The warning reuses the uptime max of 30 years used by the > > setitimeofday(). > > > > Note that the warning is only added for new filesystem mounts > > through the mount syscall. Automounts do not have the same warning. > [...] > > Another thing - perhaps this warning should be suppressed for read-only > mounts? Many filesystems support read only mounts only. We do fill in right granularities and limits for these filesystems as well. In keeping with the trend, I have added the warning accordingly. I don't think I have a preference either way. But, not warning for the red only mounts adds another if case. If you have a strong preference, I could add it in. -Deepa