> On Nov 17, 2015, at 1:07 AM, Arnd Bergmann wrote:
>
>> On Tuesday 17 November 2015 17:04:42 deng.ch...@zte.com.cn wrote:
>> Many time_t issues in filesystems is involved with VFS i_mtime/i_ctime.
>> for example:
>>
>> static void hpfs_update_directory_times(struct inode
Changes the defintion of the pointer _expiry from time_t to
time64_t. This is to handle the Y2038 problem where time_t
will overflow in 2038. The change is safe because the kernel
subsystems that call dns_query pass NULL.
Signed-off-by: Arnd Bergmann
Signed-off-by: Aya Mahfouz
You have received a new fax.
Please, download fax document attached to this email.
Scanned at:Tue, 17 Nov 2015 19:33:14 +0300
Scanned by:Reginald Fritz
Resolution:600 DPI
Pages sent:4
Document name: scanned-619186.doc
Filesize: 184 Kb
Scanned in:
On Tuesday 17 November 2015 17:04:42 deng.ch...@zte.com.cn wrote:
> Many time_t issues in filesystems is involved with VFS i_mtime/i_ctime.
> for example:
>
> static void hpfs_update_directory_times(struct inode *dir)
> {
> - time_t t = get_seconds();
> + time64_t t =
Many time_t issues in filesystems is involved with VFS i_mtime/i_ctime.
for example:
static void hpfs_update_directory_times(struct inode *dir)
{
- time_t t = get_seconds();
+ time64_t t = ktime_get_real_seconds();
- if (t == dir->i_mtime.tv_sec &&
- t ==
Changes all the uses of time_t for the structs key
and key_preparsed_payload to time64_t. This also
involves the functions that use them in security/keys.
This is to handle the y2038 problem where time_t will
overflow in 2038.
Also since time_t was a long int and time64_t is long long,
uses of
On Tuesday 17 November 2015 22:56:48 Aya Mahfouz wrote:
> Changes the defintion of the pointer _expiry from time_t to
> time64_t. This is to handle the Y2038 problem where time_t
> will overflow in 2038. The change is safe because the kernel
> subsystems that call dns_query pass NULL.
>
>
On Tue, Nov 17, 2015 at 11:18:36PM +0100, Arnd Bergmann wrote:
> On Tuesday 17 November 2015 22:56:48 Aya Mahfouz wrote:
> > Changes the defintion of the pointer _expiry from time_t to
> > time64_t. This is to handle the Y2038 problem where time_t
> > will overflow in 2038. The change is safe