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

From: Paul Mackerras <[email protected]>
Date: Thu, 8 Nov 2007 15:59:12 +1100

> Not on powerpc.  On powerpc the error indication is carried separately
> in a condition register bit.  So a force_successful_syscall_return()
> call will make glibc automatically do the right thing without any
> glibc changes on powerpc.

It still won't fix the problem.

When the return value is (clock_t) -1, all the
force_successful_syscall_return() calls and glibc condition
codes checks in the world are not going to fix the application
code which checks for error using -1.
-
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:
  • Re: compat_sys_times() bogus until jiffies >= 0.
    • From: Paul Mackerras <[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]>

• Prev by Date: Re: [poll] Is the megafreeze development model broken?
• Next by Date: Re: compat_sys_times() bogus until jiffies >= 0.
• 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]