From: Arnd Bergmann <arnd@arndb.de>
To: "Yan, Zheng" <ukernel@gmail.com>
Cc: Deepa Dinamani <deepa.kernel@gmail.com>,
John Stultz <john.stultz@linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Al Viro <viro@zeniv.linux.org.uk>,
gregkh <gregkh@linuxfoundation.org>,
"Dilger, Andreas" <andreas.dilger@intel.com>,
"J. Bruce Fields" <bfields@fieldses.org>,
Chris Mason <clm@fb.com>, David Miller <davem@davemloft.net>,
David Sterba <dsterba@suse.com>,
Evgeniy Dushistov <dushistov@mail.ru>,
Eric Paris <eparis@redhat.com>, Jaegeuk Kim <jaegeuk@kernel.org>,
Josef Bacik <jbacik@fb.com>,
Jeff Layton <jlayton@poochiereds.net>,
James Simmons <jsimmons@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
"Drokin, Oleg" <oleg.drokin@intel.com>,
Paul Moore <paul@paul-moore.com>,
Steven Rostedt <rostedt@goodmis.org>,
yuchao0@huawei.com, ceph-devel <ceph-devel@vger.kernel.org>,
devel@driverdev.osuosl.org, linux-audit@redhat.com,
linux-btrfs <linux-btrfs@vger.kernel.org>,
linux-cifs@vger.kernel.org, "Linux F2FS DEV,
Mailing List" <linux-f2fs-devel@lists.sourceforge.net>,
Linux FS-devel Mailing List <linux-fsdevel@vger.kernel.org>,
linux-mtd <linux-mtd@lists.infradead.org>,
LSM List <linux-security-module@vger.kernel.org>,
Lustre Development List <lustre-devel@lists.lustre.org>,
Networking <netdev@vger.kernel.org>,
samba-technical@lists.samba.org,
y2038 Mailman List <y2038@lists.linaro.org>
Subject: Re: [PATCH 04/12] fs: ceph: CURRENT_TIME with ktime_get_real_ts()
Date: Fri, 2 Jun 2017 16:18:26 +0200 [thread overview]
Message-ID: <CAK8P3a1etuRz6zwytXTHqK-T0g2YnbR4zcCwo98ehjjD1Dj+Ow@mail.gmail.com> (raw)
In-Reply-To: <CAAM7YA=f74Wye8hgqR52CNG-c4Sh3sm74AzZYhSnhjN1B=G-Ow@mail.gmail.com>
On Fri, Jun 2, 2017 at 2:18 PM, Yan, Zheng <ukernel@gmail.com> wrote:
> On Fri, Jun 2, 2017 at 7:33 PM, Arnd Bergmann <arnd@arndb.de> wrote:
>> On Fri, Jun 2, 2017 at 1:18 PM, Yan, Zheng <ukernel@gmail.com> wrote:
>> What I meant is another related problem in ceph_mkdir() where the
>> i_ctime field of the parent inode is different between the persistent
>> representation in the mds and the in-memory representation.
>>
>
> I don't see any problem in mkdir case. Parent inode's i_ctime in mds is set to
> r_stamp. When client receives request reply, it set its in-memory inode's ctime
> to the same time stamp.
Ok, I see it now, thanks for the clarification. Most other file systems do this
the other way round and update all fields in the in-memory inode structure
first and then write that to persistent storage, so I was getting confused about
the order of events here.
If I understand it all right, we have three different behaviors in ceph now,
though the differences are very minor and probably don't ever matter:
- in setattr(), we update ctime in the in-memory inode first and then send
the same time to the mds, and expect to set it again when the reply comes.
- in ceph_write_iter write() and mmap/page_mkwrite(), we call
file_update_time() to set i_mtime and i_ctime to the same
timestamp first once a write is observed by the fs and then take
two other timestamps that we send to the mds, and update the
in-memory inode a second time when the reply comes. ctime
is never older than mtime here, as far as I can tell, but it may
be newer when the timer interrupt happens between taking the
two stamps.
- in all other calls, we only update the inode (and/or parent inode)
after the reply arrives.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
To: "Yan, Zheng" <ukernel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: yuchao0-hv44wF8Li93QT0dZR+AlfA@public.gmane.org,
"J. Bruce Fields"
<bfields-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>,
Chris Mason <clm-b10kYP2dOMg@public.gmane.org>,
linux-mtd
<linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
Deepa Dinamani
<deepa.kernel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Evgeniy Dushistov <dushistov-JGs/UdohzUI@public.gmane.org>,
Jeff Layton <jlayton-vpEMnDpepFuMZCB2o+C8xQ@public.gmane.org>,
ceph-devel <ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
devel-gWbeCf7V1WCQmaza687I9mD2FQJk+8+b@public.gmane.org,
linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Paul Moore <paul-r2n+y4ga6xFZroRs9YW3xA@public.gmane.org>,
y2038 Mailman List
<y2038-cunTk1MwBs8s++Sfvej+rw@public.gmane.org>,
Ingo Molnar <mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Steven Rostedt <rostedt-nx8X9YLhiw1AfugRpC6u6w@public.gmane.org>,
"Drokin,
Oleg" <oleg.drokin-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
John Stultz <john.stultz-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Al Viro <viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org>,
David Sterba <dsterba-IBi9RG/b67k@public.gmane.org>,
Jaegeuk Kim <jaegeuk-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>,
Josef Bacik <jbacik-b10kYP2dOMg@public.gmane.org>,
gregkh <gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>,
samba-technical-w/Ol4Ecudpl8XjKLYN78aQ@public.gmane.org,
Linux Kernel Mailing List
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Eric Par
Subject: Re: [PATCH 04/12] fs: ceph: CURRENT_TIME with ktime_get_real_ts()
Date: Fri, 2 Jun 2017 16:18:26 +0200 [thread overview]
Message-ID: <CAK8P3a1etuRz6zwytXTHqK-T0g2YnbR4zcCwo98ehjjD1Dj+Ow@mail.gmail.com> (raw)
In-Reply-To: <CAAM7YA=f74Wye8hgqR52CNG-c4Sh3sm74AzZYhSnhjN1B=G-Ow-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Fri, Jun 2, 2017 at 2:18 PM, Yan, Zheng <ukernel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> On Fri, Jun 2, 2017 at 7:33 PM, Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org> wrote:
>> On Fri, Jun 2, 2017 at 1:18 PM, Yan, Zheng <ukernel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>> What I meant is another related problem in ceph_mkdir() where the
>> i_ctime field of the parent inode is different between the persistent
>> representation in the mds and the in-memory representation.
>>
>
> I don't see any problem in mkdir case. Parent inode's i_ctime in mds is set to
> r_stamp. When client receives request reply, it set its in-memory inode's ctime
> to the same time stamp.
Ok, I see it now, thanks for the clarification. Most other file systems do this
the other way round and update all fields in the in-memory inode structure
first and then write that to persistent storage, so I was getting confused about
the order of events here.
If I understand it all right, we have three different behaviors in ceph now,
though the differences are very minor and probably don't ever matter:
- in setattr(), we update ctime in the in-memory inode first and then send
the same time to the mds, and expect to set it again when the reply comes.
- in ceph_write_iter write() and mmap/page_mkwrite(), we call
file_update_time() to set i_mtime and i_ctime to the same
timestamp first once a write is observed by the fs and then take
two other timestamps that we send to the mds, and update the
in-memory inode a second time when the reply comes. ctime
is never older than mtime here, as far as I can tell, but it may
be newer when the timer interrupt happens between taking the
two stamps.
- in all other calls, we only update the inode (and/or parent inode)
after the reply arrives.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-security-module@vger.kernel.org
Subject: [PATCH 04/12] fs: ceph: CURRENT_TIME with ktime_get_real_ts()
Date: Fri, 2 Jun 2017 16:18:26 +0200 [thread overview]
Message-ID: <CAK8P3a1etuRz6zwytXTHqK-T0g2YnbR4zcCwo98ehjjD1Dj+Ow@mail.gmail.com> (raw)
In-Reply-To: <CAAM7YA=f74Wye8hgqR52CNG-c4Sh3sm74AzZYhSnhjN1B=G-Ow@mail.gmail.com>
On Fri, Jun 2, 2017 at 2:18 PM, Yan, Zheng <ukernel@gmail.com> wrote:
> On Fri, Jun 2, 2017 at 7:33 PM, Arnd Bergmann <arnd@arndb.de> wrote:
>> On Fri, Jun 2, 2017 at 1:18 PM, Yan, Zheng <ukernel@gmail.com> wrote:
>> What I meant is another related problem in ceph_mkdir() where the
>> i_ctime field of the parent inode is different between the persistent
>> representation in the mds and the in-memory representation.
>>
>
> I don't see any problem in mkdir case. Parent inode's i_ctime in mds is set to
> r_stamp. When client receives request reply, it set its in-memory inode's ctime
> to the same time stamp.
Ok, I see it now, thanks for the clarification. Most other file systems do this
the other way round and update all fields in the in-memory inode structure
first and then write that to persistent storage, so I was getting confused about
the order of events here.
If I understand it all right, we have three different behaviors in ceph now,
though the differences are very minor and probably don't ever matter:
- in setattr(), we update ctime in the in-memory inode first and then send
the same time to the mds, and expect to set it again when the reply comes.
- in ceph_write_iter write() and mmap/page_mkwrite(), we call
file_update_time() to set i_mtime and i_ctime to the same
timestamp first once a write is observed by the fs and then take
two other timestamps that we send to the mds, and update the
in-memory inode a second time when the reply comes. ctime
is never older than mtime here, as far as I can tell, but it may
be newer when the timer interrupt happens between taking the
two stamps.
- in all other calls, we only update the inode (and/or parent inode)
after the reply arrives.
Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
To: "Yan, Zheng" <ukernel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: yuchao0-hv44wF8Li93QT0dZR+AlfA@public.gmane.org,
"J. Bruce Fields"
<bfields-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>,
Chris Mason <clm-b10kYP2dOMg@public.gmane.org>,
linux-mtd
<linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
Deepa Dinamani
<deepa.kernel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Evgeniy Dushistov <dushistov-JGs/UdohzUI@public.gmane.org>,
Jeff Layton <jlayton-vpEMnDpepFuMZCB2o+C8xQ@public.gmane.org>,
ceph-devel <ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
devel-gWbeCf7V1WCQmaza687I9mD2FQJk+8+b@public.gmane.org,
linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Paul Moore <paul-r2n+y4ga6xFZroRs9YW3xA@public.gmane.org>,
y2038 Mailman List
<y2038-cunTk1MwBs8s++Sfvej+rw@public.gmane.org>,
Ingo Molnar <mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Steven Rostedt <rostedt-nx8X9YLhiw1AfugRpC6u6w@public.gmane.org>,
"Drokin,
Oleg" <oleg.drokin-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
John Stultz <john.stultz-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Al Viro <viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org>,
David Sterba <dsterba-IBi9RG/b67k@public.gmane.org>,
Jaegeuk Kim <jaegeuk-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>,
Josef Bacik <jbacik-b10kYP2dOMg@public.gmane.org>,
gregkh <gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>,
samba-technical-w/Ol4Ecudpl8XjKLYN78aQ@public.gmane.org,
Linux Kernel Mailing List
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Eric
Subject: Re: [PATCH 04/12] fs: ceph: CURRENT_TIME with ktime_get_real_ts()
Date: Fri, 2 Jun 2017 16:18:26 +0200 [thread overview]
Message-ID: <CAK8P3a1etuRz6zwytXTHqK-T0g2YnbR4zcCwo98ehjjD1Dj+Ow@mail.gmail.com> (raw)
In-Reply-To: <CAAM7YA=f74Wye8hgqR52CNG-c4Sh3sm74AzZYhSnhjN1B=G-Ow-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Fri, Jun 2, 2017 at 2:18 PM, Yan, Zheng <ukernel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> On Fri, Jun 2, 2017 at 7:33 PM, Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org> wrote:
>> On Fri, Jun 2, 2017 at 1:18 PM, Yan, Zheng <ukernel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>> What I meant is another related problem in ceph_mkdir() where the
>> i_ctime field of the parent inode is different between the persistent
>> representation in the mds and the in-memory representation.
>>
>
> I don't see any problem in mkdir case. Parent inode's i_ctime in mds is set to
> r_stamp. When client receives request reply, it set its in-memory inode's ctime
> to the same time stamp.
Ok, I see it now, thanks for the clarification. Most other file systems do this
the other way round and update all fields in the in-memory inode structure
first and then write that to persistent storage, so I was getting confused about
the order of events here.
If I understand it all right, we have three different behaviors in ceph now,
though the differences are very minor and probably don't ever matter:
- in setattr(), we update ctime in the in-memory inode first and then send
the same time to the mds, and expect to set it again when the reply comes.
- in ceph_write_iter write() and mmap/page_mkwrite(), we call
file_update_time() to set i_mtime and i_ctime to the same
timestamp first once a write is observed by the fs and then take
two other timestamps that we send to the mds, and update the
in-memory inode a second time when the reply comes. ctime
is never older than mtime here, as far as I can tell, but it may
be newer when the timer interrupt happens between taking the
two stamps.
- in all other calls, we only update the inode (and/or parent inode)
after the reply arrives.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: "Yan, Zheng" <ukernel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: yuchao0-hv44wF8Li93QT0dZR+AlfA@public.gmane.org,
"J. Bruce Fields"
<bfields-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>,
Chris Mason <clm-b10kYP2dOMg@public.gmane.org>,
linux-mtd
<linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
Deepa Dinamani
<deepa.kernel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Evgeniy Dushistov <dushistov-JGs/UdohzUI@public.gmane.org>,
Jeff Layton <jlayton-vpEMnDpepFuMZCB2o+C8xQ@public.gmane.org>,
ceph-devel <ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
devel-gWbeCf7V1WCQmaza687I9mD2FQJk+8+b@public.gmane.org,
linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Paul Moore <paul-r2n+y4ga6xFZroRs9YW3xA@public.gmane.org>,
y2038 Mailman List
<y2038-cunTk1MwBs8s++Sfvej+rw@public.gmane.org>,
Ingo Molnar <mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Steven Rostedt <rostedt-nx8X9YLhiw1AfugRpC6u6w@public.gmane.org>,
"Drokin,
Oleg" <oleg.drokin-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
John Stultz <john.stultz-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Al Viro <viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org>,
David Sterba <dsterba-IBi9RG/b67k@public.gmane.org>,
Jaegeuk Kim <jaegeuk-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>,
Josef Bacik <jbacik-b10kYP2dOMg@public.gmane.org>,
gregkh <gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>,
samba-technical-w/Ol4Ecudpl8XjKLYN78aQ@public.gmane.org,
Linux Kernel Mailing List
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Eric
Subject: [lustre-devel] [PATCH 04/12] fs: ceph: CURRENT_TIME with ktime_get_real_ts()
Date: Fri, 2 Jun 2017 16:18:26 +0200 [thread overview]
Message-ID: <CAK8P3a1etuRz6zwytXTHqK-T0g2YnbR4zcCwo98ehjjD1Dj+Ow@mail.gmail.com> (raw)
In-Reply-To: <CAAM7YA=f74Wye8hgqR52CNG-c4Sh3sm74AzZYhSnhjN1B=G-Ow@mail.gmail.com>
On Fri, Jun 2, 2017 at 2:18 PM, Yan, Zheng <ukernel@gmail.com> wrote:
> On Fri, Jun 2, 2017 at 7:33 PM, Arnd Bergmann <arnd@arndb.de> wrote:
>> On Fri, Jun 2, 2017 at 1:18 PM, Yan, Zheng <ukernel@gmail.com> wrote:
>> What I meant is another related problem in ceph_mkdir() where the
>> i_ctime field of the parent inode is different between the persistent
>> representation in the mds and the in-memory representation.
>>
>
> I don't see any problem in mkdir case. Parent inode's i_ctime in mds is set to
> r_stamp. When client receives request reply, it set its in-memory inode's ctime
> to the same time stamp.
Ok, I see it now, thanks for the clarification. Most other file systems do this
the other way round and update all fields in the in-memory inode structure
first and then write that to persistent storage, so I was getting confused about
the order of events here.
If I understand it all right, we have three different behaviors in ceph now,
though the differences are very minor and probably don't ever matter:
- in setattr(), we update ctime in the in-memory inode first and then send
the same time to the mds, and expect to set it again when the reply comes.
- in ceph_write_iter write() and mmap/page_mkwrite(), we call
file_update_time() to set i_mtime and i_ctime to the same
timestamp first once a write is observed by the fs and then take
two other timestamps that we send to the mds, and update the
in-memory inode a second time when the reply comes. ctime
is never older than mtime here, as far as I can tell, but it may
be newer when the timer interrupt happens between taking the
two stamps.
- in all other calls, we only update the inode (and/or parent inode)
after the reply arrives.
Arnd
next prev parent reply other threads:[~2017-06-02 14:18 UTC|newest]
Thread overview: 166+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-08 0:56 [PATCH 00/12] Delete CURRENT_TIME, CURRENT_TIME_SEC and current_fs_time Deepa Dinamani
2017-04-08 0:56 ` [lustre-devel] " Deepa Dinamani
2017-04-08 0:56 ` Deepa Dinamani
2017-04-08 0:56 ` Deepa Dinamani
2017-04-08 0:56 ` [PATCH 01/12] fs: f2fs: Use ktime_get_real_seconds for sit_info times Deepa Dinamani
2017-04-08 0:56 ` [lustre-devel] " Deepa Dinamani
2017-04-08 0:56 ` Deepa Dinamani
2017-04-08 0:56 ` Deepa Dinamani
2017-04-08 0:57 ` [PATCH 02/12] trace: Make trace_hwlat timestamp y2038 safe Deepa Dinamani
2017-04-08 0:57 ` [lustre-devel] " Deepa Dinamani
2017-04-08 0:57 ` Deepa Dinamani
2017-04-08 0:57 ` Deepa Dinamani
2017-04-08 1:30 ` Steven Rostedt
2017-04-08 1:30 ` Steven Rostedt
2017-04-08 1:30 ` Steven Rostedt
2017-04-08 2:16 ` Deepa Dinamani
2017-04-08 2:16 ` [lustre-devel] " Deepa Dinamani
2017-04-08 2:16 ` Deepa Dinamani
2017-04-08 2:16 ` Deepa Dinamani
2017-04-08 2:16 ` Deepa Dinamani
2017-04-08 2:16 ` Deepa Dinamani
2017-04-08 0:57 ` [PATCH 03/12] fs: cifs: Replace CURRENT_TIME by other appropriate apis Deepa Dinamani
2017-04-08 0:57 ` [lustre-devel] " Deepa Dinamani
2017-04-08 0:57 ` Deepa Dinamani
2017-04-08 0:57 ` Deepa Dinamani
2017-04-08 0:57 ` [PATCH 04/12] fs: ceph: CURRENT_TIME with ktime_get_real_ts() Deepa Dinamani
2017-04-08 0:57 ` [lustre-devel] " Deepa Dinamani
2017-04-08 0:57 ` Deepa Dinamani
2017-04-08 0:57 ` Deepa Dinamani
2017-06-01 9:56 ` Yan, Zheng
2017-06-01 9:56 ` Yan, Zheng
2017-06-01 9:56 ` Yan, Zheng
2017-06-01 10:22 ` Arnd Bergmann
2017-06-01 10:22 ` [lustre-devel] " Arnd Bergmann
2017-06-01 10:22 ` Arnd Bergmann
2017-06-01 10:22 ` Arnd Bergmann
2017-06-01 10:22 ` Arnd Bergmann
2017-06-01 10:22 ` Arnd Bergmann
2017-06-02 0:26 ` Yan, Zheng
2017-06-02 0:26 ` Yan, Zheng
2017-06-02 0:26 ` Yan, Zheng
2017-06-02 0:26 ` Yan, Zheng
2017-06-02 0:26 ` Yan, Zheng
2017-06-02 0:36 ` John Stultz
2017-06-02 0:36 ` John Stultz
2017-06-02 0:36 ` John Stultz
2017-06-02 0:36 ` John Stultz
2017-06-02 0:36 ` John Stultz
2017-06-02 0:36 ` John Stultz
2017-06-02 0:57 ` Deepa Dinamani
2017-06-02 0:57 ` [lustre-devel] " Deepa Dinamani
2017-06-02 0:57 ` Deepa Dinamani
2017-06-02 0:57 ` Deepa Dinamani
2017-06-02 0:57 ` Deepa Dinamani
2017-06-02 0:57 ` Deepa Dinamani
2017-06-02 2:09 ` Yan, Zheng
2017-06-02 2:09 ` Yan, Zheng
2017-06-02 2:09 ` Yan, Zheng
2017-06-02 2:09 ` Yan, Zheng
2017-06-02 9:45 ` Arnd Bergmann
2017-06-02 9:45 ` [lustre-devel] " Arnd Bergmann
2017-06-02 9:45 ` Arnd Bergmann
2017-06-02 9:45 ` Arnd Bergmann
2017-06-02 9:45 ` Arnd Bergmann
2017-06-02 9:45 ` Arnd Bergmann
2017-06-02 10:10 ` Yan, Zheng
2017-06-02 10:10 ` Yan, Zheng
2017-06-02 10:10 ` Yan, Zheng
2017-06-02 10:10 ` Yan, Zheng
2017-06-02 10:10 ` Yan, Zheng
2017-06-02 10:51 ` Arnd Bergmann
2017-06-02 10:51 ` [lustre-devel] " Arnd Bergmann
2017-06-02 10:51 ` Arnd Bergmann
2017-06-02 10:51 ` Arnd Bergmann
2017-06-02 10:51 ` Arnd Bergmann
2017-06-02 10:51 ` Arnd Bergmann
2017-06-02 11:18 ` Yan, Zheng
2017-06-02 11:18 ` Yan, Zheng
2017-06-02 11:18 ` Yan, Zheng
2017-06-02 11:18 ` Yan, Zheng
2017-06-02 11:18 ` Yan, Zheng
2017-06-02 11:33 ` Arnd Bergmann
2017-06-02 11:33 ` [lustre-devel] " Arnd Bergmann
2017-06-02 11:33 ` Arnd Bergmann
2017-06-02 11:33 ` Arnd Bergmann
2017-06-02 11:33 ` Arnd Bergmann
2017-06-02 11:33 ` Arnd Bergmann
2017-06-02 12:18 ` Yan, Zheng
2017-06-02 12:18 ` Yan, Zheng
2017-06-02 12:18 ` Yan, Zheng
2017-06-02 12:18 ` Yan, Zheng
2017-06-02 12:18 ` Yan, Zheng
2017-06-02 14:18 ` Arnd Bergmann [this message]
2017-06-02 14:18 ` [lustre-devel] " Arnd Bergmann
2017-06-02 14:18 ` Arnd Bergmann
2017-06-02 14:18 ` Arnd Bergmann
2017-06-02 14:18 ` Arnd Bergmann
2017-06-02 14:18 ` Arnd Bergmann
2017-06-04 7:54 ` Yan, Zheng
2017-06-04 7:54 ` Yan, Zheng
2017-06-04 7:54 ` Yan, Zheng
2017-06-04 7:54 ` Yan, Zheng
2017-06-04 7:54 ` Yan, Zheng
2017-06-02 0:35 ` Yan, Zheng
2017-06-02 0:35 ` Yan, Zheng
2017-06-02 0:35 ` Yan, Zheng
2017-06-02 0:35 ` Yan, Zheng
2017-06-02 0:35 ` Yan, Zheng
2017-04-08 0:57 ` [PATCH 05/12] fs: ufs: Use ktime_get_real_ts64() for birthtime Deepa Dinamani
2017-04-08 0:57 ` [lustre-devel] " Deepa Dinamani
2017-04-08 0:57 ` Deepa Dinamani
2017-04-08 0:57 ` Deepa Dinamani
2017-04-08 0:57 ` [PATCH 06/12] audit: Use timespec64 to represent audit timestamps Deepa Dinamani
2017-04-08 0:57 ` [lustre-devel] " Deepa Dinamani
2017-04-08 0:57 ` Deepa Dinamani
2017-04-08 0:57 ` Deepa Dinamani
2017-04-08 12:40 ` Paul Moore
2017-04-08 12:40 ` Paul Moore
2017-04-08 12:40 ` Paul Moore
2017-04-08 17:58 ` Deepa Dinamani
2017-04-08 17:58 ` [lustre-devel] " Deepa Dinamani
2017-04-08 17:58 ` Deepa Dinamani
2017-04-08 17:58 ` Deepa Dinamani
2017-04-08 17:58 ` Deepa Dinamani
2017-04-08 17:58 ` Deepa Dinamani
2017-04-11 20:12 ` Paul Moore
2017-04-11 20:12 ` Paul Moore
2017-04-11 20:12 ` Paul Moore
2017-04-11 20:12 ` Paul Moore
2017-04-11 20:12 ` Paul Moore
2017-04-15 10:29 ` Arnd Bergmann
2017-04-15 10:29 ` [lustre-devel] " Arnd Bergmann
2017-04-15 10:29 ` Arnd Bergmann
2017-04-15 10:29 ` Arnd Bergmann
2017-04-15 10:29 ` Arnd Bergmann
2017-04-08 0:57 ` [PATCH 07/12] fs: btrfs: Use ktime_get_real_ts for root ctime Deepa Dinamani
2017-04-08 0:57 ` [lustre-devel] " Deepa Dinamani
2017-04-08 0:57 ` Deepa Dinamani
2017-04-08 0:57 ` Deepa Dinamani
2017-04-12 13:42 ` David Sterba
2017-04-12 13:42 ` [lustre-devel] " David Sterba
2017-04-12 13:42 ` David Sterba
2017-04-12 13:42 ` David Sterba
2017-04-08 0:57 ` [PATCH 08/12] fs: ubifs: Replace CURRENT_TIME_SEC with current_time Deepa Dinamani
2017-04-08 0:57 ` [lustre-devel] " Deepa Dinamani
2017-04-08 0:57 ` Deepa Dinamani
2017-04-08 0:57 ` Deepa Dinamani
2017-04-08 0:57 ` [PATCH 09/12] lustre: Replace CURRENT_TIME macro Deepa Dinamani
2017-04-08 0:57 ` [lustre-devel] " Deepa Dinamani
2017-04-08 0:57 ` Deepa Dinamani
2017-04-08 0:57 ` Deepa Dinamani
2017-04-08 0:57 ` [PATCH 10/12] apparmorfs: Replace CURRENT_TIME with current_time() Deepa Dinamani
2017-04-08 0:57 ` [lustre-devel] " Deepa Dinamani
2017-04-08 0:57 ` Deepa Dinamani
2017-04-08 0:57 ` Deepa Dinamani
2017-06-02 7:29 ` John Johansen
2017-06-02 7:29 ` John Johansen
2017-06-02 7:29 ` John Johansen
2017-04-08 0:57 ` [PATCH 11/12] time: Delete CURRENT_TIME_SEC and CURRENT_TIME Deepa Dinamani
2017-04-08 0:57 ` [lustre-devel] " Deepa Dinamani
2017-04-08 0:57 ` Deepa Dinamani
2017-04-08 0:57 ` Deepa Dinamani
2017-04-08 0:57 ` [PATCH 12/12] time: Delete current_fs_time() function Deepa Dinamani
2017-04-08 0:57 ` [lustre-devel] " Deepa Dinamani
2017-04-08 0:57 ` Deepa Dinamani
2017-04-08 0:57 ` Deepa Dinamani
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=CAK8P3a1etuRz6zwytXTHqK-T0g2YnbR4zcCwo98ehjjD1Dj+Ow@mail.gmail.com \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=andreas.dilger@intel.com \
--cc=bfields@fieldses.org \
--cc=ceph-devel@vger.kernel.org \
--cc=clm@fb.com \
--cc=davem@davemloft.net \
--cc=deepa.kernel@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=dsterba@suse.com \
--cc=dushistov@mail.ru \
--cc=eparis@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=jaegeuk@kernel.org \
--cc=jbacik@fb.com \
--cc=jlayton@poochiereds.net \
--cc=john.stultz@linaro.org \
--cc=jsimmons@infradead.org \
--cc=linux-audit@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-security-module@vger.kernel.org \
--cc=lustre-devel@lists.lustre.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=oleg.drokin@intel.com \
--cc=paul@paul-moore.com \
--cc=rostedt@goodmis.org \
--cc=samba-technical@lists.samba.org \
--cc=tglx@linutronix.de \
--cc=ukernel@gmail.com \
--cc=viro@zeniv.linux.org.uk \
--cc=y2038@lists.linaro.org \
--cc=yuchao0@huawei.com \
/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.