Re: compat_sys_times() bogus until jiffies >= 0.

Andreas Schwab wrote:

A possible remedy is to return the ticks since process start time, which
delays the wrap around much further.  POSIX only demands consistency
within the same process.

This would be an interesting solution.

The man page for linux states that the return code is time since system boot, so that could realistically be expected to correlate between different processes.

Could we get away with changing the man page and breaking any apps relying on this previously-documented behaviour?

Chris
-
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: compat_sys_times() bogus until jiffies >= 0.
    • From: Ulrich Drepper <[email protected]>

• References:
  • Re: compat_sys_times() bogus until jiffies >= 0.
    • From: Andrew Morton <[email protected]>
  • Re: compat_sys_times() bogus until jiffies >= 0.
    • From: Andrew Morton <[email protected]>
  • Re: compat_sys_times() bogus until jiffies >= 0.
    • From: Paul Mackerras <[email protected]>
  • Re: compat_sys_times() bogus until jiffies >= 0.
    • From: David Miller <[email protected]>
  • Re: compat_sys_times() bogus until jiffies >= 0.
    • From: Andreas Schwab <[email protected]>

• Prev by Date: Re: [PATCH (2.6.25) 0/2] suspend/hibernate Kconfig cleanups
• Next by Date: Re: [patch 02/23] SLUB: Rename NUMA defrag_ratio to remote_node_defrag_ratio
• Previous by thread: Re: compat_sys_times() bogus until jiffies >= 0.
• Next by thread: Re: compat_sys_times() bogus until jiffies >= 0.
• 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]