From: Theodore Ts'o <tytso@mit.edu>
To: "Lukáš Czerner" <lczerner@redhat.com>
Cc: Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH -v2 2/3] mke2fs: print extra information about existing ext2/3/4 file systemsGjj
Date: Wed, 7 May 2014 10:54:26 -0400 [thread overview]
Message-ID: <20140507145426.GD28814@thunk.org> (raw)
In-Reply-To: <alpine.LFD.2.00.1405071534070.2128@localhost.localdomain>
On Wed, May 07, 2014 at 03:43:09PM +0200, Lukáš Czerner wrote:
> so the whole thing should look like:
>
> + if (sb->s_mtime) {
> + tm = sb->s_mtime;
> + if (sb->s_last_mounted[0]) {
> + memset(buf, 0, sizeof(buf));
> + strncpy(buf, sb->s_last_mounted,
> + sizeof(sb->s_last_mounted));
> + printf(_("\tlast mounted on %s on %s"), buf,
> + ctime(&tm));
> + } else
> + printf(_("\tlast mounted on %s"), ctime(&tm));
> + } else if (sb->s_mkfs_time) {
> + tm = sb->s_mkfs_time;
> + printf(_("\tcreated on %s"), ctime(&tm));
> + } else if (sb->s_wtime) {
> + tm = sb->s_wtime;
> + printf(_("\tlast modified on %s"), ctime(&tm));
> + }
Sorry, that's in fact what I have.
> Also I wonder whether we need to use 'tm' variable, can't we use the
> sb->s_*time directly ? But that's nitpicking.
That's because sb->s_mkfs_time is a __u32, and time_t isn't
necessarily be a 32-bit type (and in fact isn't on x86_64, x32,
apropos of current discussion happening on ksummit-discuss.) Yes,
that means the ext4 superblock has a 2038 problem, but that's a
separate issue that we should fix one of these days....
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-05-07 14:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 1:02 [PATCH -v2 1/3] mke2fs: print a message when creating a regular file Theodore Ts'o
2014-05-06 1:02 ` [PATCH -v2 2/3] mke2fs: print extra information about existing ext2/3/4 file systems Theodore Ts'o
2014-05-06 13:42 ` Lukáš Czerner
2014-05-07 2:46 ` Theodore Ts'o
2014-05-07 8:15 ` Lukáš Czerner
2014-05-07 12:39 ` [PATCH -v2 2/3] mke2fs: print extra information about existing ext2/3/4 file systemsG Theodore Ts'o
2014-05-07 13:43 ` [PATCH -v2 2/3] mke2fs: print extra information about existing ext2/3/4 file systemsGjj Lukáš Czerner
2014-05-07 14:54 ` Theodore Ts'o [this message]
2014-05-06 1:02 ` [PATCH -v2 3/3] mke2fs: check for a partition table and warn if present Theodore Ts'o
2014-05-06 13:47 ` Lukáš Czerner
2014-05-06 13:23 ` [PATCH -v2 1/3] mke2fs: print a message when creating a regular file Lukáš Czerner
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=20140507145426.GD28814@thunk.org \
--to=tytso@mit.edu \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.