> However if you know the cases where time is set implicitly by the > server, why can't you simply optimise away the ATTR_CTIME and/or > ATTR_MTIME? How? By checking whether ATTR_SIZE is also set? Yes, that would work for truncate(), but it's rather more ugly than the proposed check for IS_NOCMTIME. 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/
- Follow-Ups:
- Re: ctime set by truncate even if NOCMTIME requested
- From: Miklos Szeredi <[email protected]>
- Re: ctime set by truncate even if NOCMTIME requested
- References:
- ctime set by truncate even if NOCMTIME requested
- From: Steve French <[email protected]>
- Re: ctime set by truncate even if NOCMTIME requested
- From: Trond Myklebust <[email protected]>
- Re: ctime set by truncate even if NOCMTIME requested
- From: Steve French <[email protected]>
- Re: ctime set by truncate even if NOCMTIME requested
- From: Trond Myklebust <[email protected]>
- Re: ctime set by truncate even if NOCMTIME requested
- From: Trond Myklebust <[email protected]>
- ctime set by truncate even if NOCMTIME requested
- Prev by Date: Re: p = kmalloc(sizeof(*p), )
- Next by Date: Re: RT bug with 2.6.13-rt4 and 3c905c tornado
- Previous by thread: Re: ctime set by truncate even if NOCMTIME requested
- Next by thread: Re: ctime set by truncate even if NOCMTIME requested
- Index(es):
