[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABeXuvruROn7j1DiCDbP6MLBt9SB4Pp3HoKqcQbUNPDJgGWLgw@mail.gmail.com>
Date: Sat, 10 Aug 2019 13:44:57 -0700
From: Deepa Dinamani <deepa.kernel@...il.com>
To: Ben Hutchings <ben.hutchings@...ethink.co.uk>
Cc: Alexander Viro <viro@...iv.linux.org.uk>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux FS-devel Mailing List <linux-fsdevel@...r.kernel.org>,
y2038 Mailman List <y2038@...ts.linaro.org>,
Arnd Bergmann <arnd@...db.de>
Subject: Re: [Y2038] [PATCH 04/20] mount: Add mount warning for impending
timestamp expiry
On Mon, Aug 5, 2019 at 7:14 AM Ben Hutchings
<ben.hutchings@...ethink.co.uk> 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
Powered by blists - more mailing lists