H. Peter Anvin wrote: > I'm a bit leery of abusing the timespec value like this, though. A > flags field seem like it would be cleaner. It's ugly. Then you have the parameter, which might have nice valid values, and they get ignored. I thought about it when this was discussed in the working group and thought it's a toss up. > Something else... if we're dickering with these interfaces, shouldn't we > allow setting atime as well? Why? To allow somebody to hide her/his tracks? -- ➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
Attachment:
signature.asc
Description: OpenPGP digital signature
- Follow-Ups:
- Re: [PATCH] utimensat implementation
- From: "H. Peter Anvin" <[email protected]>
- Re: [PATCH] utimensat implementation
- References:
- [PATCH] utimensat implementation
- From: Ulrich Drepper <[email protected]>
- Re: [PATCH] utimensat implementation
- From: Andrew Morton <[email protected]>
- Re: [PATCH] utimensat implementation
- From: "H. Peter Anvin" <[email protected]>
- [PATCH] utimensat implementation
- Prev by Date: RE: W1 printk format warning
- Next by Date: Re: linux-2.6.21 and __udivid3
- Previous by thread: Re: [PATCH] utimensat implementation
- Next by thread: Re: [PATCH] utimensat implementation
- Index(es):