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

From: Andrew Morton <[email protected]>
Date: Wed, 7 Nov 2007 21:20:05 -0800

> Yup.  But userspace will already have a fit if either the start or end time
> advanced into the glibc-thought-that-was-an-error range.

On x86 only.  We could use force_successful_syscall_return()
to make sure the condition codes get set correctly on
other platforms.

But even in that case we'd still be broken when the return
value is exactly -1 and that's what the application is going
to compare against to test for errors.
-
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: Paul Mackerras <[email protected]>
  • Re: compat_sys_times() bogus until jiffies >= 0.
    • From: Andrew Morton <[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: Paul Mackerras <[email protected]>
  • Re: compat_sys_times() bogus until jiffies >= 0.
    • From: Andrew Morton <[email protected]>

• Prev by Date: Re: compat_sys_times() bogus until jiffies >= 0.
• Next by Date: Re: Use of virtio device IDs
• 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]