From: Jan Kara <jack@suse.cz>
To: Arnd Bergmann <arnd@kernel.org>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
linux-fsdevel@vger.kernel.org, Thomas Schmitt <scdbackup@gmx.net>,
stable@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Jan Kara <jack@suse.cz>, Jeff Layton <jlayton@kernel.org>,
Deepa Dinamani <deepa.kernel@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] isofs: prevent file time rollover after year 2038
Date: Mon, 24 Oct 2022 16:51:21 +0200 [thread overview]
Message-ID: <20221024145121.2dj6sdeqvxndbhpt@quack3> (raw)
In-Reply-To: <20221024122614.bkcehqr7gi3f23ca@quack3>
On Mon 24-10-22 14:26:14, Jan Kara wrote:
> On Thu 20-10-22 18:00:29, Arnd Bergmann wrote:
> > From: Thomas Schmitt <scdbackup@gmx.net>
> >
> > Change the return type of function iso_date() from int to time64_t,
> > to avoid truncating to the 1902..2038 date range.
> >
> > After this patch, the reported timestamps should fall into the
> > range reported in the s_time_min/s_time_max fields.
> >
> > Signed-off-by: Thomas Schmitt <scdbackup@gmx.net>
> > Cc: stable@vger.kernel.org
> > Link: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800627
> > Fixes: 34be4dbf87fc ("isofs: fix timestamps beyond 2027")
> > Fixes: 5ad32b3acded ("isofs: Initialize filesystem timestamp ranges")
> > [arnd: expand changelog text slightly]
> > Signed-off-by: Arnd Bergmann <arnd@arndb.de>
>
> Thanks! I've added the patch to my tree and will push it to Linus.
Oh, I have noticed Andrew has merged the patch already into his tree. So
dropped from mine.
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2022-10-24 16:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 16:00 Arnd Bergmann
2022-10-21 9:19 ` Christian Brauner
2022-10-21 12:41 ` Jeff Layton
2022-10-24 12:26 ` Jan Kara
2022-10-24 14:51 ` Jan Kara [this message]
2022-10-24 20:55 ` Andrew Morton
2022-10-25 9:26 ` Jan Kara
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221024145121.2dj6sdeqvxndbhpt@quack3 \
--to=jack@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=deepa.kernel@gmail.com \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=scdbackup@gmx.net \
--cc=stable@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®