Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1434690 > unrolled thread
| Started by | Theodore Ts'o <tytso@mit.edu> |
|---|---|
| First post | 2016-06-30 18:00 +0200 |
| Last post | 2016-06-30 18:00 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH] jbd2: make journal y2038 safe Theodore Ts'o <tytso@mit.edu> - 2016-06-30 18:00 +0200
| From | Theodore Ts'o <tytso@mit.edu> |
|---|---|
| Date | 2016-06-30 18:00 +0200 |
| Subject | Re: [PATCH] jbd2: make journal y2038 safe |
| Message-ID | <rPMxJ-2YZ-49@gated-at.bofh.it> |
On Sun, Jun 19, 2016 at 05:53:47PM +0200, Jan Kara wrote: > On Fri 17-06-16 17:39:00, Arnd Bergmann wrote: > > The jbd2 journal stores the commit time in 64-bit seconds and 32-bit > > nanoseconds, which avoids an overflow in 2038, but it gets the numbers > > from current_kernel_time(), which uses 'long' seconds on 32-bit > > architectures. > > > > This simply changes the code to call current_kernel_time64() so > > we use 64-bit seconds consistently. > > > > Signed-off-by: Arnd Bergmann <arnd@arndb.de> > > The patch looks good. You can add: > > Reviewed-by: Jan Kara <jack@suse.cz> Applied, thanks. - Ted
Back to top | Article view | linux.kernel
csiph-web