On 06/19/2016 07:27 PM, Deepa Dinamani wrote: > jfs uses nanosecond granularity for filesystem timestamps. > Only this assignemt is not using nanosecond granularity. > Use current_time() to get the right granularity. > > Signed-off-by: Deepa Dinamani <deepa.ker...@gmail.com> > Cc: jfs-discussion@lists.sourceforge.net
Acked-by: Dave Kleikamp <dave.kleik...@oracle.com> > --- > fs/jfs/ioctl.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/fs/jfs/ioctl.c b/fs/jfs/ioctl.c > index 8653cac..b6fd1ff 100644 > --- a/fs/jfs/ioctl.c > +++ b/fs/jfs/ioctl.c > @@ -121,7 +121,7 @@ long jfs_ioctl(struct file *filp, unsigned int cmd, > unsigned long arg) > > jfs_set_inode_flags(inode); > inode_unlock(inode); > - inode->i_ctime = CURRENT_TIME_SEC; > + inode->i_ctime = current_time(inode); > mark_inode_dirty(inode); > setflags_out: > mnt_drop_write_file(filp); > ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. http://sdm.link/zohomanageengine _______________________________________________ Jfs-discussion mailing list Jfs-discussion@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jfs-discussion
