On Thu, Jun 9, 2016 at 1:38 PM, Deepa Dinamani wrote:
>
> 1. There are a few link, rename functions which assign times like this:
>
> - inode->i_ctime = dir->i_ctime = dir->i_mtime = CURRENT_TIME;
> + inode->i_ctime = dir->i_ctime = dir->i_mtime =
> current_fs_time(dir->i_sb);
So I th
On Thu, Jun 9, 2016 at 12:08 PM, Linus Torvalds
wrote:
> On Wed, Jun 8, 2016 at 10:04 PM, Deepa Dinamani
> wrote:
>> CURRENT_TIME macro is not appropriate for filesystems as it
>> doesn't use the right granularity for filesystem timestamps.
>> Use current_fs_time() instead.
>
> Again - using the
Hi,
Before this patch, function read_rindex_entry would set a rgrp
glock's gl_object pointer to itself before inserting the rgrp into
the rgrp rbtree. The problem is: if another process was also reading
the rgrp in, and had already inserted its newly created rgrp, then
the second call to read_rind
On Wed, Jun 8, 2016 at 10:04 PM, Deepa Dinamani wrote:
> CURRENT_TIME macro is not appropriate for filesystems as it
> doesn't use the right granularity for filesystem timestamps.
> Use current_fs_time() instead.
Again - using the inode instead fo the syuperblock in tghis patch
would have made th
for nilfs2 bits:
Acked-by: Ryusuke Konishi
Thanks,
Ryusuke Konishi
Hi,
GFS2 bits:
Acked-by: Steven Whitehouse
Steve.
The series is aimed at getting rid of CURRENT_TIME and CURRENT_TIME_SEC macros.
The macros are not y2038 safe. There is no plan to transition them into being
y2038 safe.
ktime_get_* api's can be used in their place. And, these are y2038 safe.
All filesystem timestamps use current_fs_time() for the
CURRENT_TIME macro is not appropriate for filesystems as it
doesn't use the right granularity for filesystem timestamps.
Use current_fs_time() instead.
CURRENT_TIME is also not y2038 safe.
This is also in preparation for the patch that transitions
vfs timestamps to use 64 bit time and hence make
On Wed, Jun 08, 2016 at 10:04:48PM -0700, Deepa Dinamani wrote:
> CURRENT_TIME macro is not appropriate for filesystems as it
> doesn't use the right granularity for filesystem timestamps.
> Use current_fs_time() instead.
>
> CURRENT_TIME is also not y2038 safe.
>
> This is also in preparation fo
Hi,
Deepa Dinamani writes:
> drivers/usb/gadget/function/f_fs.c | 2 +-
> drivers/usb/gadget/legacy/inode.c | 2 +-
for drivers/usb/gadget:
Acked-by: Felipe Balbi
--
balbi
signature.asc
Description: PGP signature
10 matches
Mail list logo