Re: [PATCH 2.6] Do not set ATTR_CTIME in do_truncate(). - was: Re: truncate(2) sometimes updates ctime and sometimes ctime and mtime!

> Here is a (tested) patch to remove the setting of ATTR_CTIME in
> do_truncate() as you suggested.

This is still inconsistent: all other "setattr" operations (chmod,
chown, chgrp, utime) still set ATTR_CTIME.

I think either ATTR_CTIME should be implicit in ->setattr() in which
case you should remove it in all those cases, or leave it as it is.

Miklos
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

References:
- [PATCH 2.6] Do not set ATTR_CTIME in do_truncate(). - was: Re: truncate(2) sometimes updates ctime and sometimes ctime and mtime!
  - From: Anton Altaparmakov <[email protected]>

Prev by Date: Re: halt: init exits/panic
Next by Date: [email protected] mailbomb
Previous by thread: [PATCH 2.6] Do not set ATTR_CTIME in do_truncate(). - was: Re: truncate(2) sometimes updates ctime and sometimes ctime and mtime!
Next by thread: [email protected] mailbomb
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]