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

On Tue, 29 Aug 2006, Jeremy Fitzhardinge wrote:
>
> There doesn't seem much point; nothing seems to use it on the trap-handling
> paths.  Is it a historical left-over?

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.

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

References:
- Why set ORIG_EAX(%esp) to -1 in arch/i386/kernel/entry.S:error_code?
  - From: Jeremy Fitzhardinge <[email protected]>

Prev by Date: [PATCH] ext3 should use uint for internal inode containers
Next by Date: [PATCH] Allow file systems to manually d_move() inside of ->rename()
Previous by thread: Why set ORIG_EAX(%esp) to -1 in arch/i386/kernel/entry.S:error_code?
Next by thread: Re: Why set ORIG_EAX(%esp) to -1 in arch/i386/kernel/entry.S:error_code?
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]