Re: Why set ORIG_EAX(%esp) to -1 in arch/i386/kernel/entry.S:error_code?

Linus Torvalds wrote:

No. It's important that ORIG_EAX be set to some value that is _not_ a valid system call number, so that the system call restart logic (see the signal handling code) doesn't trigger.

Ah, yes, I see.  I'll add a comment in my i386-pda patch to entry.S.

   J
-
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:
  • Why set ORIG_EAX(%esp) to -1 in arch/i386/kernel/entry.S:error_code?
    • From: Jeremy Fitzhardinge <[email protected]>
  • Re: Why set ORIG_EAX(%esp) to -1 in arch/i386/kernel/entry.S:error_code?
    • From: Linus Torvalds <[email protected]>

• Prev by Date: Re: [PATCH 4/18] 2.6.17.9 perfmon2 patch for review: new system calls support
• Next by Date: Re: [PATCH] kthread: saa7134-tvaudio.c
• Previous by thread: Re: Why set ORIG_EAX(%esp) to -1 in arch/i386/kernel/entry.S:error_code?
• Next by thread: end_swap_bio_write error handling
• 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]