On Sun, Jan 21, 2018 at 6:04 PM, Deepa Dinamani wrote:
> + t.tv_nsec -= t.tv_nsec % gran;
This doesn't actuall ywork if tv_nsec is negative.
Which may not be an issue in most cases, but did somebody check
utimensat() or whatever?
> + WARN(1,
On Tue, Apr 25, 2017 at 1:31 PM, Arnd Bergmann wrote:
>
> Would it be ok to have a simple way of removing the time_t definition (e.g.
> by passing '-DREQUIRE_TIME64' to the compiler, but without the Kconfig
> option? That way, someone who wants to ship a product can at least
> find
On Tue, Apr 25, 2017 at 12:47 PM, Arnd Bergmann wrote:
>
> There is one global option that I want to see, and that is for completely
> disabling all components that are known to be broken in y2038.
I really don't see the point.
Don't do it. Make it some local hack, I'm not taking
On Sat, Apr 8, 2017 at 12:37 PM, Deepa Dinamani wrote:
> Allow read only mounts for filesystems that do not
> have maximum timestamps beyond the y2038 expiry
> timestamp.
This option seems arbitrary and pointless.
Nobody sane should ever enable it except for testing, but
On Wed, Sep 14, 2016 at 7:48 AM, Deepa Dinamani wrote:
> 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.
This version looks ok to me.
Al,
On Sun, Jun 19, 2016 at 5:26 PM, Deepa Dinamani wrote:
> The series is aimed at getting rid of CURRENT_TIME and CURRENT_TIME_SEC
> macros.
This version now looks ok to me.
I do have a comment (or maybe just a RFD) for future work.
It does strike me that once we
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 =
>
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
On Thu, Jun 9, 2016 at 12:35 AM, Jan Kara wrote:
>
> You create line longer than 80 characters for affs and reiserfs. Please
> wrap those lines properly.
No, please do *NOT* do things like that.
These kind of mechanical patches should
(a) be as mechanical as possible (and see
On Wed, Jun 8, 2016 at 10:04 PM, Deepa Dinamani wrote:
> CURRENT_TIME_SEC and CURRENT_TIME are not y2038 safe.
> current_fs_time() will be transitioned to be y2038 safe
> along with vfs.
>
> current_fs_time() returns timestamps according to the
> granularities set in the
10 matches
Mail list logo